Excerpts from Sven Joachim's message of Mon Jul 14 17:58:24 +0200 2014:
> On 2014-07-14 12:12 +0200, Michal Suchanek wrote:
>
> > 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.
>
> Looks normal.
>
> > 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?
>
> Would be nice, but don't reboot just for that.
>
> Which parameters do you set, BTW? It's quite possible that some
> /proc/sys entry does not exist when systemd-sysctl.service runs because
> the necessary kernel module has not yet been loaded . Newer versions of
> the sysctl.d manpage[1] contain this warning:
Ok, here is status after booting:
OptiPlex960:/home/hramrach# systemctl status systemd-sysctl.service
systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
Active: active (exited) since Tue 2014-07-15 11:15:21 CEST; 2h 49min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 342 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.
OptiPlex960:/home/hramrach# sysctl -a | grep dirty
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 40
vm.dirty_bytes = 0
vm.dirty_expire_centisecs = 3000
vm.dirty_ratio = 60
vm.dirty_writeback_centisecs = 60000
OptiPlex960:/home/hramrach# /etc/init.d/procps start
[ ok ] Setting kernel variables ...done.
OptiPlex960:/home/hramrach# sysctl -a | grep dirty
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 2
vm.dirty_bytes = 0
vm.dirty_expire_centisecs = 3000
vm.dirty_ratio = 5
vm.dirty_writeback_centisecs = 60000
OptiPlex960:/home/hramrach# systemctl status systemd-sysctl.service
systemd-sysctl.service - Apply Kernel Variables
Loaded: loaded (/lib/systemd/system/systemd-sysctl.service; static)
Active: active (exited) since Tue 2014-07-15 11:15:21 CEST; 2h 49min ago
Docs: man:systemd-sysctl.service(8)
man:sysctl.d(5)
Process: 342 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.
As you can see the variables have changed after starting the service manually.
I don't think this falls under the 'does not exist on boot' category.
If it does how does one set the values, anyway?
They do need to be set.
Thanks
Michal
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
