[systemd-devel] usefulness of swap.target

Zbigniew Jędrzejewski-Szmek zbyszek at in.waw.pl
Thu Nov 3 04:06:27 PDT 2011


I have a missing (because of some udev/lvm problem, yet undiagnosed) 
swap device. During boot this causes a timeout, but then the information 
about this problem is not very visible:
- I get a message that a unit timed out because of dependency problems
- dev-mapper-beck\x2dswap_1.swap is dead
- systemctl doesn't print anything in red (which would be the first
              thing to check for service problems)
- swap.target is alive

This is somehow not very user friendly -- if something which is 
configured in /etc/fstab fails, the failure should be more explicit.

Also, swap.target only 'wants' the swap units, but I think that it 
should 'require' them, like local-fs.target 'requires' mount units 
generated from /etc/fstab. Right now I have an 'active' swap.target with 
all of the swaps dead, which is kind of misleading.

Just complaining :)


More information about the systemd-devel mailing list