SIGHUP fails to restart (3.6.1p2 -> 3.7p1)

Darren Tucker dtucker at
Sun Sep 21 22:44:38 EST 2003

Phil Howard wrote:
> I have the sshd daemon located at /sbin/ssh_22 in this scenario (because I have
> more than one daemon with separate executable images).  After upgrading from
> 3.6.1p2 to 3.7p1, with the /sbin/ssh_22 copy replaced by mv (not by writing
> over the existing image), I do SIGHUP and get this message logged:

> 2. Was 3.6.1p2 broken in that respect?

Saving argv[0] was broken in 3.6.1p2 in some cases, it's since been fixed.

Darren Tucker (dtucker at
GPG key 8FF4FA69 / D9A3 86E9 7EEE AF4B B2D4  37C9 C982 80C7 8FF4 FA69
    Good judgement comes with experience. Unfortunately, the experience
usually comes from bad judgement.

More information about the openssh-unix-dev mailing list