bugzilla-daemon at mindrot.org
2004-Feb-24 10:28 UTC
[Bug 529] sshd doesn't work correctly after SIGHUP
http://bugzilla.mindrot.org/show_bug.cgi?id=529 postadal at suse.cz changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From postadal at suse.cz 2004-02-24 21:28 ------- This problem is re-appeared in new 3.7.1p2 version with added followed lines on position 832: #ifndef HAVE_SETPROCTITLE /* Prepare for later setproctitle emulation */ compat_init_setproctitle(ac, av); av = saved_argv; ^^^^^^^^^^^^^^^^ #endif The new patch follows in attachment. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2004-Feb-24 10:29 UTC
[Bug 529] sshd doesn't work correctly after SIGHUP
http://bugzilla.mindrot.org/show_bug.cgi?id=529 postadal at suse.cz changed: What |Removed |Added ---------------------------------------------------------------------------- Attachment #301 is|0 |1 obsolete| | ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2004-Feb-24 10:31 UTC
[Bug 529] sshd doesn't work correctly after SIGHUP
http://bugzilla.mindrot.org/show_bug.cgi?id=529 ------- Additional Comments From postadal at suse.cz 2004-02-24 21:31 ------- Created an attachment (id=552) --> (http://bugzilla.mindrot.org/attachment.cgi?id=552&action=view) New patch for re-apeared problem with save_argv ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
bugzilla-daemon at mindrot.org
2004-Feb-24 10:45 UTC
[Bug 529] sshd doesn't work correctly after SIGHUP
http://bugzilla.mindrot.org/show_bug.cgi?id=529 dtucker at zip.com.au changed: What |Removed |Added ---------------------------------------------------------------------------- Status|REOPENED |RESOLVED Resolution| |FIXED ------- Additional Comments From dtucker at zip.com.au 2004-02-24 21:45 ------- This is fixed in -current and will be fixed in 3.8p1 (which will be released in the next day or so). Check a snapshot to confirm. ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
Maybe Matching Threads
- [Bug 529] sshd doesn't work correctly after SIGHUP
- [Bug 529] sshd doesn't work correctly after SIGHUP
- [PATCH] ssh: set proctitle for mux master
- Why openssh newer than 2.9.9 doesn't send SIGTERM and SIGHUP to child process?
- OpenSSH build failure on NetBSD 1.5.2