[systemd-devel] systemd --test still tries to execute quite some actions and fails

Andrey Borzenkov arvidjaar at gmail.com
Fri Feb 18 02:42:58 PST 2011


Example as non-root

[bor at n2 ~]$ systemd  --system --unit=graphical.target --test > /tmp/foo
systemd 17 running in system mode. (+PAM +LIBWRAP +AUDIT -SELINUX
+SYSVINIT -LIBCRYPTSETUP; fedora)
FATAL: Could not load /lib/modules/2.6.33.7-server-2mnb/modules.dep:
No such file or directory
/sbin/modprobe failed with error code 1.
Failed to set hostname to <n2.mandriva.com>: Operation not permitted
Netlink failure for request 1: Operation not permitted
Failed to configure loopback device: Operation not permitted
/etc/mtab is not a symlink or not pointing to /proc/self/mounts. This
is not supported anymore. Please make sure to replace this file by a
symlink to avoid incorrect or misleading mount(8) output.
Failed to enable ctrl-alt-del handling: Operation not permitted
Failed to open /dev/tty0: Permission denied
Failed to allocate manager object: No such file or directory


example as root in chroot

[iurt cooker] rootn2/home/bor$ systemd --system
--unit=graphical.target --test > /tmp/foo
Failed to mount /sys/fs/cgroup: No such file or directory

well ... this makes --test rather useless. I definitely do not want it
to mess with anything on live system. All it is expected to do is
"Determine startup sequence, dump it and exit.", *not* trying to
mount, modprobe, etc etc


More information about the systemd-devel mailing list