Bug#778913: openssh-server: init (at least systemd) doesn't notice when sshd fails to start and reports success

Michael Biebl biebl at debian.org
Tue May 12 21:54:04 BST 2015


Am 12.05.2015 um 17:42 schrieb Michael Biebl:
> Am 12.05.2015 um 17:07 schrieb Michael Biebl:

>> As you can see, systemd tries to repeatedly start the service until it hits
>> start-limit.
>> We should use sd_notify in that case to pass a correct error code to systemd.
> 
> Or we could use what's been proposed by Colin, i.e.
>  ExecStartPre=/usr/bin/sshd -t
> or my
>  RestartPreventExitStatus=255

Updated patch, adding RestartPreventExitStatus=, attached.

From my limited testing, seems to work fine here.


-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: sshd-v2.diff
Type: text/x-patch
Size: 3846 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150512/0c619900/attachment-0002.bin>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20150512/0c619900/attachment-0002.sig>


More information about the Pkg-systemd-maintainers mailing list