Hi Tollef,
Tollef Fog Heen tfh...@err.no writes:
]] Michael Biebl
Am 02.07.2013 04:38, schrieb Paul Wise:
systemd doesn't support environment initctl requests. systemd needs to
support all initctl requests if it is going to replace sysvinit in Debian
Why is
On Tue, 2013-07-02 at 08:19 +0200, Michael Stapelberg wrote:
Paul, could you clarify what’s the actual problem here? You did not say
whether anything actually went wrong, e.g. did your machine not power
off even though you requested it (but you said it _was_ powered off)?
I didn't request a
Hi Paul,
Paul Wise p...@debian.org writes:
mechanisms did a shutdown. The machine was off when I woke up. The only
issue is that this caused a warning because systemd doesn't implement
some required stuff. I have no idea what uses that initctl feature but
there are bound to be some things
Package: systemd
Version: 44-12
Severity: normal
My machine was overheating and it shutdown (as per usual) but when
investigating why it was powered off, I found a message saying that
systemd doesn't support environment initctl requests. systemd needs to
support all initctl requests if it is
Am 02.07.2013 04:38, schrieb Paul Wise:
systemd doesn't support environment initctl requests. systemd needs to
support all initctl requests if it is going to replace sysvinit in Debian
Why is INIT_CMD_SETENV/INIT_CMD_UNSETENV a critical feature which needs
to be supported by systemd-initctl?
]] Michael Biebl
Am 02.07.2013 04:38, schrieb Paul Wise:
systemd doesn't support environment initctl requests. systemd needs to
support all initctl requests if it is going to replace sysvinit in Debian
Why is INIT_CMD_SETENV/INIT_CMD_UNSETENV a critical feature which needs
to be
6 matches
Mail list logo
