On Tue, Nov 20, 2012 at 08:52:51AM -0500, Daniel J Walsh wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 11/19/2012 07:41 PM, Lennart Poettering wrote: > > On Fri, 16.11.12 15:06, Daniel J Walsh (dwa...@redhat.com) wrote: > > > >> Isn't there a way to shut off systemV init scripts altogether, it just > >> so happens that we hit one on my machine. But in the field a customer > >> could have an init script and then setup containers and systemd will > >> attempt to start it. I want a way to say don't run SysV Init scripts > >> altogether. > > > > Hmm, there is currently no option for that. > > > > A semi-dirty trick might be to over-bind-mount /etc/rc.d with something > > empty? > > > > Lennart > > > What run levels would get executed? I would prefer to mount over the empty > run levels and allow an admin to be able to turn on a SysV init script.
I'm not convinced we need to support that explicitly. If an admin wants to support execution of some ad-hoc script they can easily make a system unit that uses the various ExecXXX directives to invoke their arbitrary shell scripts. Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
