[NTLUG:Discuss] ssh login

[MadHat]

On Wed, 2002-08-07 at 13:41, Kenneth Loafman wrote:
> If I kill the bash session associated with the sshd, the session
> terminates and the user is logged out.  If I kill the sshd instead, I
> see some of the same behavior, login survives, but only until the next
> reboot.
> 
> So, kill the session, not the daemon.  Just a workaround.

Good suggestion.  I think it does depend on what signal you send though
(IIRC).  For instance a SIGINT (interupt, -2) is like using a CTRL-C and
will shut it down properly and register it with the utmp, but a SIGKILL
(kill -9) forces it to die and does not always allow the process to
"logout" before being destroyed.  This is also by design.

> 
> ...Ken
> 
> > TJ Davis wrote:
> > 
> > so do you have a solution as to how to fix the problem?  The first and
> > only suggestion did not work.
> > 
> > T.J. Davis
> > Southwestern A/G University
> > Information Technology
> > tjdavis at sagu.edu
> > (972) 937-4010 ext. 1255
> > 1 Timothy 4:12
> > 
> > -----Original Message-----
> > From: MadHat [mailto:madhat at unspecific.com]
> > Sent: Wednesday, August 07, 2002 3:18 AM
> > To: NTLUG-Discuss
> > Subject: Re: [NTLUG:Discuss] ssh login
> > 
> > On Tue, 2002-08-06 at 06:47, Greg Edwards wrote:
> > > I've seen this on my machines as well.  I've even seen the login
> > stay
> > > registered after a reboot.  Never did try to figure it out.
> > 
> > This was actually answered, but just to make sure...  when you log
> > into
> > a box, it makes an entry into the /var/run/utmp (may be different on
> > different distributions).  When you log out, another entry is made.
> > If
> > you do not log out, but lose your connection, this will cause the
> > logout
> > entry to be not registered.  Also you can have your shell still
> > running
> > at times, if it did not receive the proper signal.  This can also
> > traverse reboots since the logout entry will still not exist (not the
> > shell still running).
> > 
> > utmp (and wtmp, the backup usually located in /var/log) contain info
> > also used by the 'last' command to say when people were logged in and
> > how long they were on and other bits of info like when the machine was
> > 
> > rebooted (and the kernel version often).  I prefer 'w 'to 'who', as it
> > 
> > adds some more info about the idle time and what they are running by
> > default, but it still relies on the utmp file.
> > 
> > >
> > > TJ Davis wrote:
> > >
> > > > command prompt.  To test this I logged into ssh remotely as
> > "tjdavis"
> > > > and killed the daemon while logged in.  I went into the server
> > room and
> > > > typed "who" and sure enough it shows tjdavis to still be logged
> > in.
> > > > Anyone know how to fix this.  I hope I made sense.  If you need
> > > > clarification let me know.
> > > >
> > > > T.J. Davis
> > >
> > >
> > > --
> > > Greg Edwards
> > > New Age Software, Inc.
> > > http://www.nas-inet.com
> > >
> > >
> > > _______________________________________________
> > > http://www.ntlug.org/mailman/listinfo/discuss
> > >
> > --
> > MadHat at Unspecific.com
> > "Anyone who understands Linux/Unix, really understands the universe.
> >  Anyone who understands Windows, really understands Windows."
> >           - Richard Thieme, DefCon 10, 2002
> > 
> > _______________________________________________
> > http://www.ntlug.org/mailman/listinfo/discuss
> 
> _______________________________________________
> http://www.ntlug.org/mailman/listinfo/discuss
> 
-- 
MadHat at Unspecific.com
"Anyone who understands Linux/Unix, really understands the universe.
 Anyone who understands Windows, really understands Windows."
          - Richard Thieme, DefCon 10, 2002