Mailinglist Archive: yast-devel (53 mails)

< Previous Next >
[yast-devel] What means calling Service.[Start|Stop|Enable|Disable]("foo")?


when there is one service foo with two systemd unit files
foo.service and foo.socket and a YaST module calls
what is each call meant to result in the system?

Does calling Service.[Start|Stop|Enable|Disable]("foo") mean
both foo.service and foo.socket get started/stopped/enabled/disabled
does calling Service.[Start|Stop|Enable|Disable]("foo") mean
only foo.service gets started/stopped/enabled/disabled?

I would expect that calling Service.[Start|Stop|Enable|Disable]("foo")
means "the whole 'foo' thing" (both foo.service and foo.socket)
while calling Service.[Start|Stop|Enable|Disable]("foo.service")
means only foo.service (but not foo.socket).

See in particular
that reads [it was YCP at that time (openSUSE 12.3)]
... the YCP call Service::Stop("foo")
should completely stop those service in all ways
how those service can be active or semi-active via systemd.

This way Service::Stop("foo") would work for systemd
in compliance how it worked all the time for SysVinit
and all YaST modules that use Service::Stop("foo")
would work the same for systemd and SysVinit.

In contrast if Service::Stop("foo") only stops foo.service
but not foo.socket, foo.path (and all other possible ways
which may exist in systemd), then Service::Stop("foo")
would be basically useless functionality for systemd
because if e.g. foo.socket is still active, any normal user
can activate the service by triggering systemd via the socket

Kind Regards
Johannes Meixner
SUSE LINUX Products GmbH -- Maxfeldstrasse 5 -- 90409 Nuernberg -- Germany
HRB 16746 (AG Nuernberg) GF: Jeff Hawn, Jennifer Guild, Felix Imendoerffer
To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >
Follow Ups