search for: wtmpx_write_entry

...02 (07:16) fuga 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...

...sh 3.8.1p1, two entries are written to /etc/wtmp and /etc/wtmpx each time a user logs in via ssh. This can be demonstrated using the last(C) command. Any user connected via ssh will have two identical login and logout entries. On SCO, login_write() in loginrec.c calls both wtmp_write_entry() and wtmpx_write_entry() (USE_WTMP and USE_WTMPX are defined). wtmp_write_entry() writes the first entry to /etc/wtmp. wtmpx_write_entry() ultimately calls updwtmpx() (HAVE_UPDWTMPX is defined) to write the /etc/wtmpx entry. But updwtmpx() writes entries to both the wtmp and wtmpx files on SCO, so now we have two entrie...

...quot;$Id: loginrec.c,v 1.32 2001/02/22 21:23:21 stevesk Exp $"); @@ -173,6 +174,8 @@ # include <libutil.h> #endif +extern ServerOptions options; + /** ** prototypes for helper functions in this file **/ @@ -438,7 +441,8 @@ utmpx_write_entry(li); #endif #ifdef USE_WTMPX - wtmpx_write_entry(li); + if (!options.use_login) + wtmpx_write_entry(li); #endif return 0; } Index: session.c =================================================================== RCS file: /cvs/openssh_cvs/session.c,v retrieving revision 1.100 diff -u -r1.100 session.c --- session.c 2001/03/22 02:06:57 1.100 +++...

...o avoid modifying wtmpx when also modifying utmpx fixes things up nicely: Index: loginrec.c --- loginrec.c 2001/05/08 20:33:06 1.33 +++ loginrec.c 2001/06/06 17:14:25 @@ -456,9 +456,10 @@ # endif # ifdef USE_UTMPX utmpx_write_entry(li); -# endif -# ifdef USE_WTMPX +# else +# ifdef USE_WTMPX wtmpx_write_entry(li); +# endif # endif return 0; } Now running "last -10" after logging in has only a single entry for each ssh user, rather than a totally bogus entry before each valid entry. I'd be interested in knowing if this works properly on UNICOS or not. ..wayne..

...p_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 wtmpx_write_entry(li); +# endif # endif return 0; } ---8<------8<------8<------8<---cut here--->8------>8------>8------>8---

...@@ 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 + /** ** getlast_entry: Call low-level functions to retrieve the last login ** time. Index: loginrec.h --- loginrec.h 2001/02/05 12:42:18 1.5 +++ loginrec.h 2001/04/29 18:12:41 @@ -110,6 +110,9 @@ /* record the entry */ int login_login (str...

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