Mailing List Archive

[Bug 529] sshd doesn't work correctly after SIGHUP
http://bugzilla.mindrot.org/show_bug.cgi?id=529

postadal@suse.cz changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|RESOLVED |REOPENED
Resolution|FIXED |



------- Additional Comments From postadal@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.
[Bug 529] sshd doesn't work correctly after SIGHUP [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=529

postadal@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.
[Bug 529] sshd doesn't work correctly after SIGHUP [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=529





------- Additional Comments From postadal@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.
[Bug 529] sshd doesn't work correctly after SIGHUP [ In reply to ]
http://bugzilla.mindrot.org/show_bug.cgi?id=529

dtucker@zip.com.au changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|REOPENED |RESOLVED
Resolution| |FIXED



------- Additional Comments From dtucker@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.