similar to: 64 bits/solaris : last/utmp/wtmp error

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

It appears to be a pervasive assumption in the Portable OpenSSH code that wtmp and wtmpx records for the end of a session do not need to include the user name or hostname. Unfortunately Solaris appears not to go along with that assumption; the Solaris "last" command shows all login sessions initiated by OpenSSH as never terminating, or sometimes terminating with the user's next

Hi :-) i have rollout a new ssh pakage in our environment. Apr 27 12:06:03 systemx sshd[869]: [ID 847 auth.info] wtmp_write: problem writing /var/adm/wtmp: No such file or directory Solaris 8 has no /var/adm/wtmp, it use /var/adm/wtmpx In the old package there was many of this messages I compiled the new package with --disable-wtmp \ --enable-wtmpx \ but sometimes one of this message are in

I am using the "UseLogin yes" configuration parameter to call the /usr/bin/login program on SGI Irix, (we are using Irix version 6.5.13). I do this because the SGI login program is AFS awhere and checks out a token for you and I do not want to compile the Kerberos version of sshd, (it is to messy for me to support). Everything seems to work fine accept the wtmp(x) and utmp(x) files do

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

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

sessreg is used by display managers such as xdm and gdm to record X sessions in utmp, wtmp, and lastlog files. This release attempts to clean up some inconsistencies around the handling of the various files. Long long ago, Unix systems had a utmp file to record who was currently logged in, and a wtmp file to record login history. Long ago, extended versions of the files & APIs for them were

I spent some time with 3.0.2p1 to discover why OpenSSH on HP/UX 11.00 64-bit corrupts the /var/adm/wtmp file. The problem is with the utmp structure itself. When building with 32-bit compilation flags, the size of the utmp structure is 60 bytes. When building under 64-bit, the size is 72 bytes. The size difference is due to structure alignment and using basic types whose size changes depending

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

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

Hi! I have updated to OpenSSH 2.9p1 on HP-UX 10.20. Since this update, I seem to have problems with utmp/wtmp handling, in that entries are not removed as expected. ws01 36: w 10:06am up 76 days, 12:52, 12 users, load average: 0.17, 0.25, 0.20 User tty login@ idle JCPU PCPU what ... root pts/8 5:28pm159:41 - ... ws01 37: ps -ef | grep pts/8

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

Hi, For each user connection when privilege separation is enabled, 3 processes are of interest for this topic. 1. sshd:[priv] - privileged user process. 2. sshd:user at pts/0 - user process. 3. shell - shell process. Openssh code writes the #2. sshd:user at pts/0 - user process to the utmp/wtmp file. Is this the correct behaviour.? Or should it write the #3. shell

http://bugzilla.mindrot.org/show_bug.cgi?id=337 Summary: utmp/wtmp logging Product: Portable OpenSSH Version: 3.1p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: enhancement Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: thomas at

https://bugzilla.mindrot.org/show_bug.cgi?id=2111 Bug ID: 2111 Summary: Android does not properly implement utmp or wtmp. Product: Portable OpenSSH Version: 6.2p1 Hardware: All OS: Linux Status: NEW Severity: minor Priority: P5 Component: Build system Assignee: unassigned-bugs

Good day - I've checked where I can think to check, but I can find no mention of wtmp/utmp being supported in the standard Samba release at all. The closest I got was a posting from Joshua Lewis <jlewis@iosphere.net> dated Fri, 19 Jul 1996 08:06:55 -0400 (EDT) (almost exactly a year ago) which states in the final paragraph: > On another note, look for UTMP/WTMP support in Samba

I'm seeing a problem using OpenSSH v2.9.9p2 on solaris and the usage of the "last" command. The "last <username>" usage is displaying the sessions as still being logged on the server when it's really not. The "last" by itself shows correct information about the session. Sometimes using the "last <username>" syntax the session shows

http://bugzilla.mindrot.org/show_bug.cgi?id=337 markus at openbsd.org changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |INVALID ------- Additional Comments From markus at openbsd.org 2002-07-05

Hi there, I'm using samba-2.2.2 under Solaris 8 and I've got the following problem! I have configured samba with "--with-utmp" and with "--with-quota" and everything works fine. But when look for the last users logged in, in the utmp-database there are only the first seven letters of the username, not eight that we use for usernames. Can you help me with this problem

Hi! I am resending the following message about problems with utmp handling. * In the meantime I had some request in private mail from people asking whether I have new information. * The problem is still persistant in 2.9p2. * My own new investigations show, that the problem only appears with protocol 2, not with protocol 1, I therefore only started to note it when protocol 2 became the