| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
|
|
|
| |
'systemctl list-unit-files' returns the enabled/disabled status for all
native systemd services. So we only need to call 'systemctl is-enabled'
for the generated services.
This reduces clutter in the installer log file.
|
| |
|
|
| |
category.
|
| | |
|
| |
|
|
|
| |
Better to add new descriptions for socket-activated services rather
than try to reuse existing ones.
|
| | |
|
| |
|
|
| |
This filters out static services that can't be enabled or disabled.
|
| |
|
|
|
|
|
| |
Several systemd units that the user may wish to enable or disable (e.g.
fstrim.timer, saned.socket) are not wanted by the multi-user or graphical
targets. So also show units that are wanted by the sockets or timers
targets (better too much than too little).
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
| |
Since systemd 246 it adds some characters at the beginning
of the line which break parsing when --plain is not set (mga#27046)
|
| |
|
|
|
|
| |
systemd has migrated to cgroups v2, so the old test no longer works.
Instead, test for the existence of /run/systemd/system as described
in https://www.freedesktop.org/software/systemd/man/sd_booted.html.
|
| | |
|
| | |
|
| |
|
|
| |
Resolves: mga#6286
|
| |
|
|
| |
(because of previous commits)
|
| |
|
|
|
|
|
|
|
|
|
| |
Some services such as shorewall are not "wantedby".
However, as systemd is not running during installation, we failed to
detect if whether they're enabled or not as the legacy fallback doesn't
handle such services
Let's try hard to query status of services that are not "wanted" but
we're checking for.
Thus fixing updating firewall status after configuration (mga#17288)
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
they're obsolete since switching from CVS/SVN to git...
|
| |
|
|
|
|
|
|
|
|
| |
Basically, there seems to be an issue right now if we do lots of reloads.
It seems to be somewhat racy and systemd gets generally confused when we
do this during boot (which we do) and trigger a reload. The reload isn't
strictly needed, as we do also explicitly start the services we enable
(with --no-block so that we don't cause a deadlock) so all *should* be
99% OK. Using it at runtime might mean we don't have fully up-to-date
enablement status, but being able to boot wins at the moment.
|
| | |
|
| |
|
|
| |
See https://bugzilla.gnome.org/show_bug.cgi?id=711873
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
| |
v2 (by Colin Guthrie)
* Fix external variable reference (my -> our + $ when using it)
* Drop systemd cgroup filesystem check as the path has changed now
(prefer "systemctl is-active foo.service" instead)
* Add iburst to chrony config server definitions (triggers sync at
startup)
* Don't use ntpdate with chrony - rather chronyc waitsync
* Don't bother checking for ntp in finish-install - just use chrony
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
enabled are shown (mga#6843)
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
| | |
|
| |
|
|
| |
This could be made more complex, but it'll do for now.
|
| | |
|
| | |
|
| |
|
|
| |
enabling/disabling of services.
|
| | |
|