This is the mail archive of the cygwin mailing list for the Cygwin project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
On Wed, Dec 22, 2010 at 01:17:11PM +0300, Vasya Pupkin wrote: > On Wed, Dec 22, 2010 at 12:41 PM, Thorsten Kampe > <thorsten@XXXXXXXXXXXXXXX> wrote: http://cygwin.com/acronyms/#PCYMTNQREAIYR > > * Vasya Pupkin (Wed, 22 Dec 2010 09:26:29 +0300) > >> I have a problem running cygwin sshd. I often end up with a lot of > >> bash processes running and eating memory while there are no single > >> active ssh session. It happens when either connection lost or user > >> closes connection without logging out, sshd process dies but bash > >> remains in memory forever. Is it possible to prevent this? In all real > >> unix environments this never happen, bash always dies when parent sshd > >> exits. You might want to enable TCPKeepAlive. It could, at a very least, prevent disconnections without explicit user interaction. $ grep -i keepalive /etc/ssh*config /etc/ssh_config:TCPKeepAlive yes /etc/sshd_config:TCPKeepAlive yes Despite the man pages for ssh_config and sshd_config stating that it is enabled by default, I had to explicity declare it to prevent ssh connections _from_ a cygwin box to the outside from dying. This was a while back, though. Regards. -- Huella de clave primaria: 0FDA C36F F110 54F4 D42B D0EB 617D 396C 448B 31EB
Attachment:
signature.asc
Description: Digital signature
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |