similar to: [ANNOUNCE] sessreg 1.1.0

Joao Carlos Mendes Luis <jonny@coe.ufrj.br> wrote: > I think it would be useful if samba had a utmp log interface. > I know that it's possible to see who is logged with smbstatus, but > sometimes a simple who(1) or w(1) is more efficient and ubiquitous. If you were to search for 'wtmp' in the 1997 archives (via the Samba web pages), you would find one interesting

Hello When I was using OpenSSH-2.9p2 in Solaris 8 sparcv9 (64bit) environment, I found some trouble that wtmpx has broken. The size of utmpx structure object becomes larger than 32 bit environment in sparcv9 environment.Therefore, instead of using utmpx structure object, using futmpx structure object is better. In sparcv9 environment, futmpx structure object is used instead of utmpx structure

Sessreg is a simple program for managing utmp/wtmp entries for X sessions. It was originally written for use with xdm, but may also be used with other display managers such as gdm or kdm. Changes since 1.1.1: Alan Coopersmith (4): Update README for gitlab migration Update configure.ac bug URL for gitlab migration Add comment about why safe_strncpy isn't replaced with

Egbert Eich (1): Use off_t instead of long to make largefile support work Emil Velikov (1): autogen.sh: use quoted string variables Matt Turner (1): sessreg 1.1.1 Mihail Konev (1): autogen: add default patch prefix Peter Hutterer (1): autogen.sh: use exec instead of waiting for configure to finish Stefan Dirsch (1): Pass -P to the preprocessor when

Hi, I've installed openssh-2.1.0p2 on a Solaris 8 host (SPARC). The sshd corrupts utmpx/wtmpx when a client connects to this machine. Observable error: $ who who: Error --- entry has ut_type of 28265 when maximum is 9 It can be repeated and is attributable to the login done by sshd. Now, Solaris has only utmpx/wtmpx and not the old utmp/wtmp. It get's worse as more logins take place

Get this building on GNU and BSD systems. J?rg Billeter: Fix grep pattern in Makefile.am Matthieu Herrb: include <time.h> before <utmp.h>. Required on some systems. git tag: sessreg-1.0.2 http://xorg.freedesktop.org/archive/individual/app/sessreg-1.0.2.tar.bz2 MD5: bee5d87d40615e67c84ab0b0c65049ba sessreg-1.0.2.tar.bz2 SHA1: 2f2a36967ecffb29461ae28def3b013955e584dd

sessreg is used by display managers such as xdm and gdm to record X sessions in utmp, wtmp, and lastlog files. This minor maintenance release includes portability fixes for BSD systems, code cleanups, and the addition of a -V option to print the version number. Alan Coopersmith (4): Fix some clang warnings about implicit conversions Combine usage message into a single string

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Alan Coopersmith: X_NOT_POSIX bits for pre-POSIX-1990 systems not needed any more Version bump: 1.0.4 David Nusinow: Require xproto instead of libX11 for building (bug #9631) James Cloos: Add missing PHONY line for automatic ChangeLog generation git tag: sessreg-1.0.4

Problem: 'last' output is incorrect, /var/adm/wtmpx is corrupted. Example: foster pts/1 Wed Dec 31 16:00 still logged in foster pts/3 dim Thu Aug 1 14:34 still logged in Solution: (workaround) This turned out to be an OpenSSH problem! If OpenSSH (only tested versions 3.4p1 and 3.5p1) is compiled 64-bit it corrupts the /var/adm/wtmpx

Hi, Solaris (tested with 2.6) needs a username in the logout record in the wtmpx file. Currently openssh (version 2.3.0p1) leaves the username (utmpx.ut_user) empty in logout records, which leads to conflicting results from the last command. Example: # last -5 siegert siegert pts/186 stikine.ucs.sfu. Mon Jan 15 14:26 still logged in siegert pts/105 stikine.ucs.sfu. Mon Jan 15

On SCO 5.0.7 and openssh 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()

Hi, Attached is a patch to 1.2.1pre18 that includes a number of portability changes, and more a more complete HPUX10.20 implementation. Thanks to Ben Taylor's utmpx patch, utmpx and wtmpx support are now in for HP, with a few caveats. It compiles cleanly on HPUX10.20 with gcc, cleanly on Linux, and with a few minor warnings on Solaris 2.6. Most compat changes are made via autoconf which

Using UseLogin on a system that has to twiddle utmpx before calling login currently also twiddles wtmpx, and this causes problems on Solaris in the "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

I was having problems getting the UseLogin option to work on Solaris. I would recieve this error: No utmpx entry. You must exec "login" from the lowest level "shell". This led me to believe that Solaris login wants a utmpx entry in order to function. I put together a patch that calls record_login on Solaris when using the system login. I also noticed that writing a wtmpx

We're trying to build OpenSSH 3.0.2p1 for Solaris 8 (among others) and are running into a problem with UseLogin and utmpx. If we set "UseLogin no" then we can login okay. finger or who won't find us, even with a TTY allocated altough "who /etc/wtmpx" will find us. But the real problem is if we set "UseLogin true" which we must do for BSM support on some

I'm using openssh 2.5.2p2 on Solaris-x86 2.6. I ran into a couple problems when I set UseLogin to "yes": The big one seems to have been reported before: login refuses to run without a utmpx entry. This problem appears to have been caused by the changes in revision 1.24 of session.c. Before this revision, the record_login() function was always called, no matter how UseLogin was

Hi, A lot of the problems with openssh portability so far appear to be with the login record functionality, i.e. lastlog support, and variations on handling utmp vs. utmpx etc. Looking at for-profit SSH 1.2.27, login.c is rather embarassing spaghetti code, so laden with '#ifdef's it's almost impossible to read. OpenSSH's code isn't anything like that, but then it doesn't

Starting with 11.23 HP is using utmps as if we didn't already have enough (utmp, wtmp, utmpx, wtmpx,... did I miss any??) . Anyway, I added support for it in (before this patch no logins from ssh were showing up on my 11.23 and 11.31 systems). http://homepage.mac.com/gagnocg/downloads/hpux-cvs.diff

Hello all, The next version of FreeBSD will use utmpx for its user accounting database, as opposed to utmp which is used right now. Unfortunately wtmpx and lastlog handling isn't standardized at all, which is why we took the liberty to integrate all these databases into a compact API, where setutxdb() can be used to switch to a different database and getutxuser() to search for a USER_PROCESS

I have some troubles with subj and proper utmpx/wtmpx functionality. After successfull ssh connect to Solaris 8 box, I run #w 11:59am up 13:45, 1 user, load average: 0.00, 0.01, 0.02 User tty login@ idle JCPU PCPU what root console 11:43am 9 bash # Record about my pts/1 login is absent. Next command I run from Solaris 8 console