Buck Huppmann
2001-Jul-18 00:15 UTC
configure: sense of --enable-utmpx test et al. reversed
it seems that --enable-utmpx and friends have the effect of disabling
the corresponding feature (i.e., #define-ing DISABLE_UTMPX etc.), which
leads to the (perhaps not so) obvious breakage of UseLogin on Solaris
etc. For the less anal (or reformed anal) configure-r who leaves these
unspecified, everything is OK
i'd suggest changes to configure.in, but i'm blissfully ignorant of
autoconf. suffice it to say, despite the help text arguments, these
macro invocations seem suspect:
^dnl allow user to disable some login recording features
AC_ARG_ENABLE(lastlog,
[ --disable-lastlog disable use of lastlog even if detected
[no]],
[ AC_DEFINE(DISABLE_LASTLOG) ]
)
AC_ARG_ENABLE(utmp,
[ --disable-utmp disable use of utmp even if detected [no]],
[ AC_DEFINE(DISABLE_UTMP) ]
)
AC_ARG_ENABLE(utmpx,
[ --disable-utmpx disable use of utmpx even if detected [no]],
[ AC_DEFINE(DISABLE_UTMPX) ]
)
etc.
other than this complaint (assuming it's valid and that i'm not
crocked),
i'm an immensely satisfied customer--thanks very much, folks
Possibly Parallel Threads
- [openssh-portable] utmpx and ut_name
- ssh hangs or gives Segmentation fault
- [Bug 1732] New: Proper utmpx support for FreeBSD HEAD
- [Bug 345] w (uptime) command still indicates user is logged in after logout
- [Bug 378] New: sshd does not update utmp/utmpx records correctly when "UseLogin" feature on
