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

Roger Qiu roger.qiu at polycademy.com
Wed Jul 16 19:40:59 PDT 2014


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?

Thanks,
Rger


More information about the systemd-devel mailing list