[arch-general] Polishing systemd
Martín Cigorraga
msx at archlinux.us
Tue Oct 16 03:25:08 EDT 2012
Hi all,
I've been playing with systemd for a few hours now and I must say I'm
impressed,
it's a very powerful tool. I want to thanks the devs for making the
transition to it
really smooth :)
Now, as I'm still learning my way through it -that means I'm reading a
lot!- I find that
there are in my system here and there some small rough edges I would like
to fix,
these rough edges are:
1. Units with errors shown in systemctl --all:
arch-modules-load.service error inactive
dead arch-modules
auditd.service error inactive
dead auditd.servi
plymouth-quit-wait.service error inactive
dead plymouth-qui
plymouth-start.service error inactive
dead plymouth-sta
rc-local-shutdown.service error inactive
dead rc-local-shu
rc-local.service error inactive
dead rc-local.ser
syslog.service error inactive
dead syslog.servi
A journalctl --this-boot shows:
Cannot add dependency job for unit arch-modules-load.service, ignoring:
Unit arch-modules-load.service failed to load: No such file or directory.
See system
logs and 'systemctl status arch-modules-load.service' for details.
That's because there isn't such file, right, but why is systemd trying to
start it in
first place?
Since I strictly followed the wiki I don't know what I did wrong, in any
case I would
like to know how to fix them.
By the way: what is the auditd.service? There's even isn't any related file
in
/lib/systemd/system.
2. KDE-related issues:
a) It seems a bit buggy to launch KDE SC through xinit: KDE's power options
will not
be present (KDE will not enable it's own reboot and shutdown options). This
don't
really worry me too much since I've read somewhere there're plans to
rebuild all login
managers to systemd-logind enabled - while dropping ConsoleKit.
b) If KDE is launched through xinit it will not see the built-in sound card
and will offer
to remove it from it's supported devices. Otherwise if KDE is initiated via
KDM every-
things works right.
c) KDM reboot and poweroff commands must be updated to systemd's way or
else the
traditional shutdown command will hang the system on reboot/shutdown.
3. $ systemctl reboot and $ systemctl shutdown features:
I feel a bit uncomfortable with the idea of having restricted users with
the hability to
reboot or shutdown the system, is there any way to change this so only r00t
can issue
these orders? (Without going dirty.)
4. Is there any place for e4rat(lite)?
Since I activated systemd's built-in ureadahead feature, will e4rat still
add any improve-
ment? What do you say?
I think that's all for now!
Once again I want to thanks everyone involved in porting systemd to AL and
making this
an overall relaxed transition, systemd is an incredible tool and I'm
delighted with it. Boot
and shutdown times are faster than ever (blazing fast to be honest),
configuration is
quite clean and easy and the journal feature is incredible useful giving a
*lot* of informa-
tion about almost everything.
Regards.
More information about the arch-general
mailing list