On Fri, May 31, 2013 at 08:29:55AM +0000, "Jóhann B. Guðmundsson" wrote: > On 05/28/2013 09:05 AM, Vaclav Pavlin wrote: > >From: Václav Pavlín<[email protected]> > > > >systemctl set-default NAME links the default.target to the given unit, > >get-default prints out the path to the currently set default target. > > Is this not a bit tricky as in dont we need a way to detect ( > introduce Bootable=yes in target units? ) if the administrator(s) > are linking to a non bootable target and error out gracefully as in > > Something like... > > systemctl set-default nfs.target > > nfs.target not bootable target exiting... Hm, we could check if the target has AllowIsolate=true, and warn otherwise. It is possible to boot to an AllowIsolate=false unit, so it shouldn't be an error.
> Bootable dependency in target not meet > nfs.target not bootable target exiting... > > otherwise users/administrators might risk linking to a non bootable > target, reboot and find themselves with an un-bootable host ( which > might be easy to deal with locally but not so much remotely )? Zbyszek _______________________________________________ systemd-devel mailing list [email protected] http://lists.freedesktop.org/mailman/listinfo/systemd-devel
