[systemd-devel] I have switched libvirt-sandbox containers to use multi-user.target

["Jóhann B. Guðmundsson"]

On 11/20/2012 01:52 PM, 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 (dwalsh at 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.

It's just nonsense to add any switch and doing so only slows down 
migration of sysv init scripts to native systemd files.

JBG