Mail Archives: cygwin/2003/10/13/13:08:00
On Mon, Oct 13, 2003 at 05:58:45PM +0100, Dr.D.J.Picton wrote:
>
> > Date: Mon, 13 Oct 2003 16:38:29 +0100 (BST)
> > From: "Dr.D.J.Picton" <dave AT aps5 DOT ph DOT bham DOT ac DOT uk>
> > Subject: Re: SSH connection close when _any_ user logs out of W2K
> > To: cygwin AT cygwin DOT com
> > Mime-Version: 1.0
> > Content-MD5: IFHKe0TcizXXvm44ktLQnA==
> >
> > > Date: Mon, 13 Oct 2003 15:08:25 +0100 (BST)
> > > From: "Dr.D.J.Picton" <dave AT aps5 DOT ph DOT bham DOT ac DOT uk>
> > > Subject: Re: SSH connection close when _any_ user logs out of W2K
>
> > > >At 05:23 PM 9/30/2003, Matthew Hilty wrote:
> > > >>Hello,
> > > >> I've noticed on a recent installation of OpenSSH under cygwin
> > > >>(followed http://tech.erdelynet.com/cygwin-sshd.html) that users
> > > >>connected to the server via SSH have their connections closed if any
> > > >>Windows user logs out of the desktop. The SSHD daemon still functions,
> > > >>it just closes active sessions. After this, I can SSH back to the
> > > >>server and my session stays active until I intentionally log out, or
> > > >>another Windows users logs in, then out.
>
> I've found a workaround! You need to tell bash to ignore SIGHUP. (This
> will also be inherited by processes started by the shell).
>
> I added the following to /etc/profile, so that the shell will ignore
> SIGHUP in an interactive session started by sshd:
>
> # Fix to sshd problem (any Windows logout kills interactive ssh sessions)
> if [ -n "$SSH_TTY" ]; then
> trap '' SIGHUP
> fi
Thanks for all that examining the situation. I found the cause of that
problem in Cygwin and it should be solved in the next version.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Developer mailto:cygwin AT cygwin DOT com
Red Hat, Inc.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://cygwin.com/docs.html
FAQ: http://cygwin.com/faq/
- Raw text -