similar to: Openssh Solaris problem writing /var/adm/wtmp

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

Hello list! Sorry to be a pain, but I've hunted high and low and can't seem to find the answer. I have a Slackware 10 system and a Microsoft Windows 2000 system. On the Windows 2000 system are lots of files with extended characters - like (tm), (r) and characters with umlauts. I used the "locale" command and set LC_ALL=en_US.UTF8. I am running KDE and in the Konqueror

Hi all, I hope someone can help, as I have an urgent problem. I've got a production Asterisk server thats been deployed, but we are seeing a strange voice echo problem. There is about a 250ms echo for the users in the office, and they are hearing their own voice back at them. I'm running the CVS Head code, on RH9.0. This is on a P4 box with 2gb of memory. The client SIP phones are

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

When I SSH using protocol 1 from a Debian box running OpenSSH 2.9p2-4 to a sparc.sunos5 box running vanilla OpenSSH 2.9.1, after a little while (of inactivity?) I get the following message on the client terminal: Disconnecting: protocol error: rcvd type 98 Looking further, this message is actually caused by the SSH daemon. However, I'm at a loss to determine why sshd is doing this. I attach

hello tried the archives without success so hoping someone remember the fix. if compiled 64 bits openssh will not add a correct entry in wtmpx and the data/info get corrupted... so someone remembers what needed to be done to fix this? thanks -ls

Hi, I hope some can help me out, as I have a problem with the vpb driver in *, and I am hoping someone has hit these issues and can offer some advice. First off, I'm connected to a British Telecom SystemX exhange with the local Tel Co. I can ring out fine, but when the callee on POTS answers, the vpb driver detects a loop drop and immediantly disconnects the call. I have currently set

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

https://bugzilla.mindrot.org/show_bug.cgi?id=1946 Bug #: 1946 Summary: AIX and /var/adm/wtmp Classification: Unclassified Product: Portable OpenSSH Version: 5.9p1 Platform: PPC OS/Version: AIX Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: unassigned-bugs at

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()

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

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

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, 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

Full_Name: Hamit AYDIN Version: R v2.1.1 OS: winxp Submission from: (NULL) (194.27.40.230) When I try to run sciviews the consol opens but when I try to import text, spss... it tries to load rmcdr pakage gives me "the pakage can not be find inthe Package or bundle 'Rcmdr' was not found in C:\PROGRA~1\R\rw2011\library. Would you like to install it now?" I know the pakage in

Hi, I just installed OpenSSH 4.3p1 on our Solaris 8 machines and 'last' now shows wtmpx entries for ssh logins like zierke pts/4 Thu Jan 1 01:00 still logged in zierke pts/3 Thu Jan 1 01:00 - 10:56 (13183+09: instead of e.g. zierke pts/3 rzdspc10.informa Sat Feb 4 10:54 - 10:54 (00:00) zierke pts/2

http://bugzilla.mindrot.org/show_bug.cgi?id=348 Summary: infinite loop scanning wtmpx Product: Portable OpenSSH Version: -current Platform: Other OS/Version: All Status: NEW Severity: normal Priority: P2 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: rodney at

http://bugzilla.mindrot.org/show_bug.cgi?id=464 Summary: sshd seems to corrupt the wtmpx Product: Portable OpenSSH Version: 3.5p1 Platform: UltraSparc OS/Version: Solaris Status: NEW Severity: minor Priority: P4 Component: sshd AssignedTo: openssh-unix-dev at mindrot.org ReportedBy: pas50

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

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