We are running 3.4p1. After upgrading to AIX 5.1, the "w" function (in ksh) stopped showing ssh logins. We upgraded to 3.6p1, no luck. Any thoughts? --- Jack Gostl gostl at argoscomp.com
Jack Gostl wrote:> We are running 3.4p1. After upgrading to AIX 5.1, the "w" function (in > ksh) stopped showing ssh logins. We upgraded to 3.6p1, no luck. > > Any thoughts?Recompile your sshd on AIX 5.1, or obtain one that was. The wtmp (or is that utmp, I always forget) structures changed between AIX 4.x and AIX 5.x. Prebuilt packages can be found: http://oss.software.ibm.com/developerworks/projects/opensshi/ http://www.zip.com.au/~dtucker/openssh/ -- Darren Tucker (dtucker at zip.com.au) GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4 37C9 C982 80C7 8FF4 FA69 Good judgement comes with experience. Unfortunately, the experience usually comes from bad judgement.
I can buy that. I have no trouble doing the rebuild. The problem is that the remote systems are only accessible through ssh. So I either figure out a smart way to shut it down, reinstall and restart through a batch file or I throw myself on the mercy of the firewall guys. (A pitifully small target.) thanks. On Sat, 23 Aug 2003, Darren Tucker wrote:> Jack Gostl wrote: > > We are running 3.4p1. After upgrading to AIX 5.1, the "w" function (in > > ksh) stopped showing ssh logins. We upgraded to 3.6p1, no luck. > > > > Any thoughts? > > Recompile your sshd on AIX 5.1, or obtain one that was. > > The wtmp (or is that utmp, I always forget) structures changed between AIX > 4.x and AIX 5.x. > > Prebuilt packages can be found: > http://oss.software.ibm.com/developerworks/projects/opensshi/ > http://www.zip.com.au/~dtucker/openssh/ > >-- Jack Gostl gostl at argoscomp.com
Hi, On Fri, Aug 22, 2003 at 08:05:58PM -0400, Jack Gostl wrote:> I can buy that. I have no trouble doing the rebuild. The problem is that > the remote systems are only accessible through ssh. So I either figure out > a smart way to shut it down, reinstall and restart through a batch file or > I throw myself on the mercy of the firewall guys. (A pitifully small > target.)Huh? Just log in, recompile, move the old sshd to "sshd.old", "make install", then kill the old *master* sshd (the one parented by "1") and restart it. Your session will stay up if you do it that way. gert -- USENET is *not* the non-clickable part of WWW! //www.muc.de/~gert/ Gert Doering - Munich, Germany gert at greenie.muc.de fax: +49-89-35655025 gert at net.informatik.tu-muenchen.de
Thanks. It works. On Sat, 23 Aug 2003, Gert Doering wrote:> Hi, > > On Fri, Aug 22, 2003 at 08:05:58PM -0400, Jack Gostl wrote: > > I can buy that. I have no trouble doing the rebuild. The problem is that > > the remote systems are only accessible through ssh. So I either figure out > > a smart way to shut it down, reinstall and restart through a batch file or > > I throw myself on the mercy of the firewall guys. (A pitifully small > > target.) > > Huh? Just log in, recompile, move the old sshd to "sshd.old", "make > install", then kill the old *master* sshd (the one parented by "1") and > restart it. > > Your session will stay up if you do it that way. > > gert >-- Jack Gostl gostl at argoscomp.com