DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…DESCRIPTION New applications should use the POSIX.1-specified "utmpx" versions of these functions; see STANDARDS. utmpname ... these functions, but instead uses #include struct u…NAME getutmp, getutmpx - copy utmp structure to utmpx, and vice versa LIBRARY Standard C library ... macros(7) */ #include void getutmp(const struct utmpx * ux , struct utmp * u …NAME getutmp, getutmpx - copy utmp structure to utmpx, and vice versa LIBRARY Standard C library ... macros(7) */ #include void getutmp(const struct utmpx * ux , struct utmp * u …timer VERSIONS For consistency with the other "utmpx" functions (see getutxent (3)), glibc provides (since ... updwtmpx (const char * wtmpx_file , const struct utmpx * utx ); This …