I've noticed that while Yast services-manager can list running or non-running
services it doesn't list non-running services that are started by a socket,
e.g.
leafnode@8-::1:119-::1:35528.service
That's fooled me before and I've since started using systemctl more, which
lists sockets, and which is probably the way I should be doing it.
But is Yast services-manager behaving entirely correctly here? I thought I
would ask.
There is also the Yast inetd module, which lists many services installed and
uninstalled, but no nntp or leafnode. It makes sense that it wouldn't handle
a systemd service, but why wouldn't it list this one particular service that
it could potentially run, when it lists many other uninstalled services?
--
Tom Hardy