similar to: [Bug 52] ssh hangs on exit

http://bugzilla.mindrot.org/show_bug.cgi?id=52 ------- Additional Comments From tsi at ualberta.ca 2004-02-29 07:10 ------- Created an attachment (id=557) --> (http://bugzilla.mindrot.org/attachment.cgi?id=557&action=view) suggested fix (against 3.8p1) I've been running with this patch on various flavours of Linux, IRIX and SunOS since last September. ------- You are

Hi, I use openssh-2.9p2 on LynxOS i386 system. sshd runs on LynxOS and ssh client on Redhat 7.0 Linux system (openssh-2.9p2 ssh client). The ssh client hangs on exit 90% of times. I don't think this is the usual hang-on-exit bug, because, there are no background processes running, I suppose. I attach the server debug messages. $ssh -V hari at lynx (From Linux) ... Password: ... lynx>

https://bugzilla.mindrot.org/show_bug.cgi?id=1598 Summary: ssh hangs up on exit Product: Portable OpenSSH Version: 4.3p2 Platform: All OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: ssh AssignedTo: unassigned-bugs at mindrot.org ReportedBy: beststory at yandex.ru

http://bugzilla.mindrot.org/show_bug.cgi?id=52 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #1075 is|0 |1 obsolete| | Attachment #1098 is|0 |1 obsolete|

http://bugzilla.mindrot.org/show_bug.cgi?id=52 djm at mindrot.org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kerry.schwab at wnco.com ------- Additional Comments From djm at mindrot.org 2003-01-07 18:14 ------- *** Bug 273 has been marked as a

https://bugzilla.mindrot.org/show_bug.cgi?id=52 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #57 from Damien Miller <djm at mindrot.org>

http://bugzilla.mindrot.org/show_bug.cgi?id=52 ------- Additional Comments From djm at mindrot.org 2002-01-23 17:37 ------- This is a known issue and has been discussed extensively on the mailings list. There is difference of opinion as to whether this is a bug or whether it is correct behaviour. A good description of the issue comes from a text file in Redhat's source RPM:

http://bugzilla.mindrot.org/show_bug.cgi?id=52 imaging at math.ualberta.ca changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #801 is|0 |1 obsolete| | ------- Comment #18 from imaging at math.ualberta.ca 2006-02-22 16:24

OK, with openssh-SNAP-20001218 I still have the problem of a hanging ssh when running (one specific) command on a server. On the server side, there's a small suid C prog (/usr/dh/mgmt/HupServer) that runs system "/usr/local/apache/bin/apachectl stop/start". Incidentally, apachectl is a shell script, hence the need for a suid wrapper for non-root users... On the client side,

https://bugzilla.mindrot.org/show_bug.cgi?id=1010 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |djm at mindrot.org --- Comment #2 from Damien Miller <djm at mindrot.org> 2008-06-13 13:42:57 --- I

https://bugzilla.mindrot.org/show_bug.cgi?id=1010 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Damien Miller <djm at mindrot.org> 2008-07-22 12:07:21 --- Mass update

https://bugzilla.mindrot.org/show_bug.cgi?id=1598 Damien Miller <djm at mindrot.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED --- Comment #4 from Damien Miller <djm at mindrot.org> --- Set all RESOLVED bugs to CLOSED with release

It is necessary to kick the state machine any time another thread blocks due to write() encountering a full buffer, to get the reader thread to learn that it must now poll on POLLOUT rather than just POLLIN. POSIX only provides two ways to do this: either poll() on a second fd (our pipe-to-self trick), or interrupt the polling with EINTR due to delivery of a signal. So, I played with the latter

Hello, The error message in the subject line occurs with the new 2.3.0 openssh version and appeared in the previous snapshots on our Solaris systems. As far as I remember it was reported, but have not seen any more about this. I have looked into it a little bit. First, the file session.c (line 1849 onwards): debug("session_exit_message: release channel %d", s->chanid);

http://bugzilla.mindrot.org/show_bug.cgi?id=52 espenra at lpl.nu changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |espenra at lpl.nu ------- Comment #25 from espenra at lpl.nu 2006-06-07 21:39 ------- (In reply to comment #24) > Anything more on

http://bugzilla.mindrot.org/show_bug.cgi?id=52 tsi at ualberta.ca changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|openssh-bugs at mindrot.org |tsi at ualberta.ca Status|ASSIGNED |NEW ------- Additional Comments From tsi at ualberta.ca 2004-07-30

https://bugzilla.mindrot.org/show_bug.cgi?id=52 leanne <njleanne at hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |njleanne at hotmail.com --- Comment #58 from leanne <njleanne at hotmail.com> 2008-05-15 17:05:09 --- (In

https://bugzilla.mindrot.org/show_bug.cgi?id=52 Volth <openssh at volth.com> changed: What |Removed |Added ---------------------------------------------------------------------------- See Also| |https://bugzilla.mindrot.or | |g/show_bug.cgi?id=2492 CC|

http://bugzilla.mindrot.org/show_bug.cgi?id=52 ------- Additional Comments From t8m at centrum.cz 2005-02-03 22:06 ------- Created an attachment (id=801) --> (http://bugzilla.mindrot.org/attachment.cgi?id=801&action=view) Patch submitted by John Bowman (bowman at math.ualberta.ca) This patch was attached to https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=39128 Also see

When the ssh-agent service is configured to be launched under systemd socket-activation, the user can inspect the status of the agent with something like: systemctl --user status ssh-agent.service If the user does: systemctl --user stop ssh-agent.service it causes the `systemd --user` supervisor to send a SIGTERM to the agent, which terminates while leaving the systemd-managed socket