Re: [gentoo-dev] eselect init

[Tom Wijsman <TomWij@gentoo.org>]

[-- Attachment #1: Type: text/plain, Size: 1361 bytes --]

On Sun, 26 May 2013 14:59:28 +0200
"J. Roeleveld" <joost@antarean.org> wrote:

> As an example. Lets say I want to test a new init-system. [SNIP] 
> If I then, accidentally, type "/etc/init.d/xyz start" when "xyz"
> hasn't been started by any means yet. What will happen?
> I would assume that openrc will try to start "xyz"?

As I said before:

> > They currently just bail out with bogus errors as far as I am aware.
> >
> >  # /etc/init.d/ntpd start
> > ntpd             | * WARNING: ntpd is already starting
> >  # /etc/init.d/ntpd stop
> > ntpd             | * ERROR: ntpd stopped by something else
> 
> See above, what about if "ntpd" wasn't running yet?

ntpd isn't running on my system and wasn't when I did that.

> > No, if you keep the init system the same as the one you boot with
> > there should be no problems.
> 
> See above, what about trying to start services using the method of the
> not-running init?

The same, feel free to emerge systemd and try to start a service; I
expect this to bail out since its dependencies aren't started, for its
dependencies to start the init system itself should be in use.

-- 
With kind regards,

Tom Wijsman (TomWij)
Gentoo Developer

E-mail address  : TomWij@gentoo.org
GPG Public Key  : 6D34E57D
GPG Fingerprint : C165 AF18 AB4C 400B C3D2  ABF0 95B2 1FCD 6D34 E57D

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 490 bytes --]