Bug#749330: systemd: The sysctl service is not started correctly at boot

[Michael Biebl]

Am 26.05.2014 20:50, schrieb Patrick Häcker:
> I guess the value dirty_writeback_centisecs defaults to 500. Other values 
> defined via sysctl have their (suspected) default value, too, after boot and 
> only change to the desired value after restarting the service manually as 
> described. Thus, I guess that the sysctl service is not started correctly, 
> although I cannot explain why systemctl should state otherwise (active, 
> success) in this case.

I suspect that systemd-sysctl set's the value correctly during boot, but
it is later reset by "some" other component.
Could you try the following: (as root)

mkdir /etc/systemd/system/systemd-sysctl.service.d/
echo -e "[Service]\nExecStartPost=/sbin/sysctl
vm.dirty_writeback_centisecs" >
/etc/systemd/system/systemd-sysctl.service.d/debug.conf

Then reboot and check the journal. The ExecStartPost command will dump
the sysctl value after it has been set by systemd-sysctl:

journalctl -b | grep sysctl	


If that turns up the correct vm.dirty_writeback_centisecs value, you
need to find the component which is responsible for changing it *after*
systemd-sysctl.service has run.


Cheers,
Michael

-- 
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140527/758f8111/attachment-0002.sig>