[systemd-devel] Socket activated SSHD service showing up as a failure when the client connection fReply-To:

[Zbigniew Jędrzejewski-Szmek]

On Thu, Jul 17, 2014 at 12:40:59PM +1000, Roger Qiu wrote:
> Hello everybody,
> 
> I recently discovered that when using a socket activated SSHD
> service on NixOS, it will show up as a failure on `sudo systemctl
> status` when the client fails the connection.
> 
> The details are in this issue: https://github.com/NixOS/nixpkgs/issues/3279
> 
> Basically all I need to do is telnet to my VM and of course fail the
> protocol, then run `sudo systemctl status` on the VM, and see 1
> extra failure.
> 
> Is this correct behaviour for a service to be considered a failure
> just because the client fails the connection protocol?
sshd chooses to exit with a failure code in this case. What we should really
do is add SuccessExitStatus= setting to the sshd at .service and ignore that
code. Is it some specific value?

Zbyszek