Re: [gentoo-dev] eselect init

["Michał Górny" <mgorny@gentoo.org>]

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

On Sat, 25 May 2013 21:55:20 +0200
Tom Wijsman <TomWij@gentoo.org> wrote:

> On Sat, 25 May 2013 21:09:47 +0200
> "J. Roeleveld" <joost@antarean.org> wrote:
> 
> > +1 for wrapper, from my understanding, symlinks for init-systems
> > can't be altered on a running system without risking strange
> > behaviour.
> 
> Exactly...
> 
>  # shutdown -h now
> 
> The system is going down for system halt NOW!s/1) (Sat May 25 21:25:41
> 2013): Excess arguments.

I don't know what is the state of your system when testing this but on
my system /sbin/telinit is a symlink to /sbin/init. So replacing
the latter also replaces telinit with something unexpected.

Of course, the solution is to make telinit point to the real sysvinit
executable. Not sure how well it will reboot then, however. It may be
necessary to also change 'halt' to use 'telinit' if it uses 'init'
directly.

> > I am assuming that should be for the user to keep in mind, but will
> > it be possible to add something that will make init.d-scripts not
> > work when systemd is running and unit-files not work when systemd is
> > not running?
> 
> 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

I think we fixed this already... well, not exactly this because openrc
used to try to actually start stuff. I would consider this a regression
since it had explanatory error messages.

-- 
Best regards,
Michał Górny

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