drakx/perl-install/services.pm, branch 14.36

(has_systemd) fix checking systemd presence after systemd merge of subpackages

2012-08-13T10:32:30+00:00

drakxservices: when listing services ensure disabled services that can be enabled are shown (mga#6843)

2012-07-26T09:09:21+00:00

(systemd_unit_exists) explain why we use -l

2012-06-03T16:44:32+00:00

(systemd_unit_exists) factorize

2012-05-23T18:25:15+00:00

services: Use no-block mode for service start/stop under systemd.

2012-04-29T11:52:09+00:00

This is perhaps the same issue as the 'cpufreq' bug on first boot,
but by changing things to use systemctl directly, I have inadvertantly
bypased the solution and reintroduced the bug.

As there is likely no reason to block, we will simply use no-block mode
unconditionally. Longer term, we may need to decide under what context
we are restarting/starting a given service (i.e. in an interactive GUI
vs from a script) and use the appropriate mode with appropriate user
feedback.

https://bugs.mageia.org/show_bug.cgi?id=4439

perl_checker cleanups

2012-04-25T16:37:36+00:00

services: Read systemd service information.

2012-04-24T20:10:47+00:00

This adds support for two different methods of working with systemd.

The first, and more complete method is to query systemd for information
about whether a service is enabled at boot. This mode requires that we
are running under systemd and thus only works for machines in interactive
mode post-install.

For the installer, we also support a more rudamentary method which
scans for unit files which contain simple install rules (i.e. only
those services which are part of the typical multi-user or graphical
targets (corresponding to runlevels 3 and 5 in the old days).

This method will not show all services but it should be enough
for the installer.

https://bugs.mageia.org/show_bug.cgi?id=3253
https://bugs.mageia.org/show_bug.cgi?id=3740
https://bugs.mageia.org/show_bug.cgi?id=4910
https://bugs.mageia.org/show_bug.cgi?id=5122

services: Use systemctl to determin if a service is active under systemd.

2012-04-24T20:10:45+00:00

services: Check for systemd unit when determining if a service exists.

2012-04-24T20:10:43+00:00

This could be made more complex, but it'll do for now.

services: Use the appropriate tool to start/stop services

2012-04-24T20:10:41+00:00