[Bug 2641] Add systemd notify code to to track running server

bugzilla-daemon at bugzilla.mindrot.org bugzilla-daemon at bugzilla.mindrot.org
Sat Mar 18 20:26:21 AEDT 2017


--- Comment #7 from Darren Tucker <dtucker at zip.com.au> ---
(In reply to Jakub Jelen from comment #6)
> Created attachment 2950 [details]
> fixed patch
> Never mind. Nothing from above resolves the race condition between
> systemd reading PID file and sshd after reexec writing it, except
> adding SD_NOTIFY code so I gave up.

What about reading the pidfile first to see if it has the correct PID
before rewriting it?  I did something like that to work around a
problem in pam_loginuid (LinuxPAM ticket #23, I'd link to it but
fedorahosted.org seems to have imploded).

Does systemd even need a pidfile?

You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.

More information about the openssh-bugs mailing list