Excerpts from Sven Joachim's message of Mon Jul 14 09:56:18 +0200 2014:
> On 2014-07-14 09:27 +0200, Michal Suchanek wrote:
>
> > I run systemd from testing.
> >
> > Yes, it's an init script that you kinda expect to work except it does
> > not.
>
> If so, that is not procps' fault, because systemd links procps.service
> to systemd-sysctl.service, which appears to be sensible.
>
> > I understand that you might want more information but this is in the
> > 'should just work' category so I have no idea what information you need.
>
> Well, systemd-sysctl just works for me. What does
> "systemctl status systemd-sysctl.service" print?
# systemctl status systemd-sysctl.service
systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
Active: active (exited) since Wed 2014-07-09 11:27:34 CEST; 5 days ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 389 ExecStart=/lib/systemd/systemd-sysctl (code=exited,
status=0/SUCCESS)
Warning: Journal has been rotated since unit was started. Log output is
incomplete or unavailable.
This is after starting the service manually.
Without starting it the system would crash quickly so I would notice.
Do you want the status after booting when the variables are not set as well?
I'm sure the system will crash for some other reason sooner or later so I will
see the status after boot again.
Thanks
Michal
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
