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:
,----
| Many sysctl parameters only become available when certain kernel modules
| are loaded. Modules are usually loaded on demand, e.g. when certain
| hardware is plugged in or network brought up. This means that
| systemd-sysctl.service(8) which runs during early boot will not
| configure such parameters if they become available after it has run. To
| set such parameters, it is recommended to add an udev(7) rule to set
| those parameters when they become available. Alternatively, a slightly
| simpler and less efficient option is to add the module to
| modules-load.d(5), causing it to be loaded statically before sysctl
| settings are applied (see example below).
`----
Cheers,
Sven
1. http://www.freedesktop.org/software/systemd/man/sysctl.d.html
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
