On Sun, 04 Feb 2018 19:52:34 -0600
Tom Hardy
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?
Hi Tom, YaST currently is trying to unify starting services on demand only with systemd sockets ( so drop module for inetd ) and as part is also considered extension of yast2 services manager to show sockets for service, but I worry I cannot say you any ETA as there are a lot of other features and bugs in queue. If you are interested I can point you to source code and we will welcome any patch. Thanks Josef -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org