On Wed, 2012-04-25 at 09:46 +0100, Colin Guthrie wrote: > 'Twas brillig, and Antonio Trande at 24/04/12 16:57 did gyre and gimble: > > Thank for your elucidation. Another my question about the services. > > > > In particular the fedora-storage-init.service (together to > > /fedora-storage-init-late.service/ and /fedora-wait-storage.service /), > > according to systemctl command, is used to "Initialize storage > > subsystems (RAID, LVM, etc.)"; ok, what does etc. mean ? Which are > > others ? :) > > > > I don't use neither LVM or RAID, if i disable > > fedora-storage-init-*.service, then they automatically restart itself at > > boot. > > > > I don't understand. > > From what I can gather, these are statically enabled in F17 (which also > means udev-settle.service is also statically configured as a dep). > > > Certainly that's what I've seen from: > systemctl status fedora-storage-init.service > > > fedora-storage-init.service - Initialize storage subsystems (RAID, LVM, > etc.) > Loaded: loaded (/lib/systemd/system/fedora-storage-init.service; > static) > ... > > See the word "static" there? That means it cannot be disabled. > > This is because, the initscripts package contains: > > /lib/systemd/system/local-fs.target.wants/fedora-storage-init-late.service > /lib/systemd/system/local-fs.target.wants/fedora-storage-init.service > > > i.e. the local-fs.tartget is statically configured to run these scripts. > > Technically, you can trash those symlinks on your install, but they will > be replaced by next initscripts upgrade.
You can mask the services and even though they will still be statically enabled, systemd will ignore them. -- Mathieu _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
