Mailinglist Archive: opensuse-factory (1578 mails)

[Wolfgang Rosenauer <wolfgang@xxxxxxxxxxxxx>]

Hi,

I might have missed important systemd information during the 12.1
development phase but haven't had to deal with it for my packages up to now.
A recent package update now introduced systemd services and I found it's
not obvious to me what to do.
It already starts with trivial questions where I have an my own
understanding but not absolutely sure.

The package provides an init script currently and now added systemd
service files.
So the following questions came to my mind:

Do I still package the sysvinit files? I guess that's a yes because we
still offer the sysvinit boot process.

The package has a sysconfig file which only takes a variable to modify
the daemon options. Can I use that for systemd as well? How to do that?

The daemon is currently started by default when installed. What happens
after the update to the new version which includes systemd files? Will
it be enabled by default? (I've actually tried the update and the
service was running afterwards so I guess it will be enabled in update
case but not for a fresh installation?)

For the service it makes a lot of sense to use systemd's socket
activation feature. So what do I need to do exactly to have the service
disabled but have the socket enabled to start the service automatically
(in terms of system configuration)? Is the only way to have
services/sockets enabled by default to modify some certain systemd
package and not from within a package installation? This sounds strange
and rather unfortunate so it's for example not possible to
install/update a package which then starts a service by default w/o
updating an official central distribution package?

I've tried to find answers to those questions in the wiki but had no luck.

Any hints?

Thanks,
 Wolfgang
-- 
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-factory+owner@xxxxxxxxxxxx