search for: use_wtmpx

Displaying 9 results from an estimated 9 matches for "use_wtmpx".

Did you mean: use_utmpx
2001 Aug 21
0
Resend: loginrec.c patch
I'm resending this patch just in case it got lost. The first hunk of the patch fixes a problem with the LOGIN_NEEDS_UTMPX support in that the date was not being set in the logininfo structure (causing wrong timestamps in the "last" log). The second hunk just omits the USE_WTMPX code in the LOGIN_NEEDS_UTMPX section if USE_UTMPX is defined. This prevents duplicate events in the last log under Solaris. Neither of these changes affect the non-LOGIN_NEEDS_UTMPX code. ..wayne.. ---8<------8<------8<------8<---cut here--->8------>8------>8------>8---...
2000 Jun 12
1
AIX and 2.1.1p1
The new login code works fine with AIX 4.3. Two nits, though. If --disable-lastlog is defined, the code still tries to slog through wtmp to determine the last login time. Is this a bug or a feature? If a feature, change the DISABLE_LASTLOG test below to WITH_AIXAUTHENTICATE. Also, a small typo in configure.in, plus an AIX tweak. --- configure.in.orig Thu Jun 8 21:58:35 2000 +++ configure.in Mon
2001 Jun 06
0
Remove duplicate "last" log messages with UseLogin
...t;last" log. Changing the source to 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...
2001 Jun 21
0
Output of last command is strange on Solaris 2.6/8 (OpenSSH 2.9p2)
...+++ openssh-2.9p2/loginrec.c Thu Jun 21 20:23:58 2001 @@ -451,15 +451,19 @@ # ifdef USE_UTMP utmp_write_entry(li); # endif +#ifndef __sun # ifdef USE_WTMP wtmp_write_entry(li); # endif +#endif # ifdef USE_UTMPX utmpx_write_entry(li); # endif +#ifndef __sun # ifdef USE_WTMPX wtmpx_write_entry(li); # endif +#endif return 0; } #endif If there is a right method of this case, please teach it. -- KITAZIMA, Tuneki NEC Informatec Systems,Ltd. tuneki at pb.jp.nec.com Shared Infrastructure and Services Division
2004 Jul 08
1
openssh 3.8.1p1 problem on SCO 5.0.7
...n 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 entries in /etc/wtmp and one in...
2001 Mar 22
0
Solaris UseLogin problem
...; RCSID("$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/2...
2007 Jan 17
0
login_get_lastlog - nss enviornment - works in shell env, doesn't work when sshd calls it.
...ems we shouldn't even try to obtain last login * time, e.g. AIX */ return (0); # elif defined(USE_WTMP) && \ (defined(HAVE_TIME_IN_UTMP) || defined(HAVE_TV_IN_UTMP)) /* retrieve last login time from utmp */ return (wtmp_get_entry(li)); # elif defined(USE_WTMPX) && \ (defined(HAVE_TIME_IN_UTMPX) || defined(HAVE_TV_IN_UTMPX)) /* If wtmp isn't available, try wtmpx */ return (wtmpx_get_entry(li)); # else /* Give up: No means of retrieving last login time */ return (0); # endif /* DISABLE_LASTLOG */ #endif /* US...
2001 Apr 29
2
PATCH: UseLogin fix for 2.9p1 (w/improved last-login time)
...43,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 + /** ** 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 */...
2001 Sep 14
8
Call for testers.
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