search for: login_utmp_on

...ct it on some versions) conf_lastlog_location="/var/adm/lastlog" AC_MSG_CHECKING(for obsolete utmp and wtmp in solaris2.x) Index: loginrec.c --- loginrec.c 2001/02/22 21:23:21 1.32 +++ loginrec.c 2001/04/29 18:12:40 @@ -443,6 +443,27 @@ return 0; } +#ifdef LOGIN_NEEDS_UTMPX +int +login_utmp_only(struct logininfo *li) +{ + li->type = LTYPE_LOGIN; +# ifdef USE_UTMP + utmp_write_entry(li); +# endif +# ifdef USE_WTMP + wtmp_write_entry(li); +# endif +# ifdef USE_UTMPX + utmpx_write_entry(li); +# endif +# ifdef USE_WTMPX + wtmpx_write_entry(li); +# endif + return 0; +} +#endif + /** **...

One other thing I noticed in the record_utmp_only() function is that it wasn't setting the timestamp in the logininfo structure. The following patch takes care of this: --- old/loginrec.c Wed Jun 6 11:12:14 2001 +++ loginrec.c Wed Jun 6 11:13:42 2001 @@ -448,6 +448,8 @@ login_utmp_only(struct logininfo *li) { li->type = LTYPE_LOGIN; + /* set the timestamp */ + login_set_current_time(li); # ifdef USE_UTMP utmp_write_entry(li); # endif ..wayne..

http://bugzilla.mindrot.org/show_bug.cgi?id=1030 Summary: sshd writes twice to wtmp when "UseLogin" is yes Product: Portable OpenSSH Version: 4.0p1 Platform: HPPA OS/Version: HP-UX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-bugs at mindrot.org

...pts/3 bar.foo.co.jp Thu Jan 1 09:00 - 12:45 (11494+03:45) hoge pts/2 foo.bar.co.jp Thu Jun 21 11:12 - 15:30 (04:17) hoge pts/2 foo.bar.co.jp Thu Jan 1 09:00 - 11:12 (11494+02:12) .... When comment on it with wtmp_write_entry and wtmpx_write_entry of login_utmp_only function, last output an usual entry. % last fuga pts/3 bar.foo.co.jp Thu Jun 21 12:45 - 20:02 (07:16) hoge pts/2 foo.bar.co.jp Thu Jun 21 11:12 - 15:30 (04:17) ... --- openssh-2.9p2.orig/loginrec.c Wed May 9 05:34:33 2001 +++ openssh-2.9p2/loginrec.c...

...er Solaris. Neither of these changes affect the non-LOGIN_NEEDS_UTMPX code. ..wayne.. ---8<------8<------8<------8<---cut here--->8------>8------>8------>8--- Index: loginrec.c --- loginrec.c 2001/08/06 23:29:17 1.34 +++ loginrec.c 2001/08/21 17:53:43 @@ -448,6 +448,8 @@ login_utmp_only(struct logininfo *li) { li->type = LTYPE_LOGIN; + /* set the timestamp */ + login_set_current_time(li); # ifdef USE_UTMP utmp_write_entry(li); # endif @@ -456,9 +458,10 @@ # endif # ifdef USE_UTMPX utmpx_write_entry(li); -# endif -# ifdef USE_WTMPX +# else +# ifdef USE_WTMPX wtmp...

Outside the known 'Hang-on-exit' bug and the Solaris 'PAM_TTY_KLUDGE' required. *WHAT* other issues *MUST* be address before 3.0 which is approaching fast? Those running NeXTStep I need conformation that it works under NeXT. My current Slab is packed in a storage unit due to a fire in my apartment complex (happened above me so I'm wrapping up dealing with that crap =). -

http://bass.directhit.com/openssh_snap/ Starting tonight I plan on tracking changes very closely with the OpenBSD tree. I need people to test the latest snapshot (9/14 at of right now) and report success or failure on compiling. I am starting this now because we are looking at a code freeze soon and I really want to ensure it compiles and runs on all existing platforms. So we (the portable