sessreg is used by display managers such as xdm and gdm to record X sessions in utmp, wtmp, and lastlog files. This release attempts to clean up some inconsistencies around the handling of the various files. Long long ago, Unix systems had a utmp file to record who was currently logged in, and a wtmp file to record login history. Long ago, extended versions of the files & APIs for them were standardized as utmpx and wtmpx. sessreg attempted to deal with all of the variants, including several other BSD vs. SysV differences beyond those listed above. Previously, sessreg 1.0.x would check for both the original and extended API's. If the extended API's were available, sessreg would compile in support for utmp, utmpx, & wtmpx, but not wtmp. Now it compiles in only utmpx & wtmpx support -- or, on ancient systems, only utmp & wtmp support. Previously, sessreg 1.0.x would allow callers to specify the paths to the utmp & wtmp files via -u & -w flags, and xdm defaulted to passing them until very recently. If these flags were passed, sessreg would use them as paths to the original API's and disable the extended API's. Due to the above, this would completely disable wtmp entries, since that code was not compiled in if wtmpx support was available. If a utmpx file path was passed to -u, sessreg would write to it with utmp API's, which could corrupt it. This especially screwed up Solaris, which has dropped the old files, but maps the old API's to write the new format to the new files. Now if -u & -w are passed to sessreg build with extended file support, they are used with the extended file API's. Alan Coopersmith (9): configure: Drop AM_MAINTAINER_MODE autogen.sh: Honor NOCONFIGURE=1 Print which option was in error along with usage message Zero initialize struct utmpx, as we already do for struct utmp If both utmp & utmpx interfaces are available, just use utmpx Stop disabling utmpx & wtmpx calls when -u & -w arguments are passed Attempt to modernize and better disentangle utmp vs. utmpx in the man page Include utmp.h if present, even if we're using utmpx interfaces sessreg 1.1.0 git tag: sessreg-1.1.0 http://xorg.freedesktop.org/archive/individual/app/sessreg-1.1.0.tar.bz2 MD5: e238c89dabc566e1835e1ecb61b605b9 SHA1: a27a476f7f39ae30a16dfa25ca07c12378cff7f0 SHA256: 551177657835e0902b5eee7b19713035beaa1581bbd3c6506baa553e751e017c PGP: http://xorg.freedesktop.org/archive/individual/app/sessreg-1.1.0.tar.bz2.sig http://xorg.freedesktop.org/archive/individual/app/sessreg-1.1.0.tar.gz MD5: 5d7eb499043c7fdd8d53c5ba43660312 SHA1: a82fffc04a7934ccb38faa29c0696c49eebff8b4 SHA256: e561edb48dfc3b0624554169c15f9dd2c3139e83084cb323b0c712724f2b6043 PGP: http://xorg.freedesktop.org/archive/individual/app/sessreg-1.1.0.tar.gz.sig -- -Alan Coopersmith- alan.coopersmith at oracle.com Oracle Solaris Engineering - http://blogs.oracle.com/alanc -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 832 bytes Desc: not available URL: <http://lists.x.org/archives/xorg-announce/attachments/20150119/69e4fd37/attachment.sig>