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

[Patrick Häcker]

>> I guess the value dirty_writeback_centisecs defaults to 500. Other values
>> defined via sysctl have their (suspected) default value, too.
> 
> Which other values?

Values like 
> vm.dirty_background_bytes = 16777216
> vm.dirty_bytes = 100663296
which I have defined in sysctl.conf, too. Yet, the output of
> cat /proc/sys/vm/dirty_{background_,}bytes
is
> 0
> 0
which I assume to be default values. As mentioned: dirty_writeback_centisecs 
is only one example. Although, on closer examination, these three values seem 
to be the only one which are not applied, the other values defined in 
sysctl.conf are applied.
The pattern seems to be, that all values inside of "vm" get discarded and all 
the other values ("net", "fs" and "kernel" tested) are taken.

Okay, so my theory is void. I'll check your next e-mail, maybe that one can 
bring light into the dark.

Btw: Thanks for your patience!
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://alioth-lists.debian.net/pipermail/pkg-systemd-maintainers/attachments/20140527/a30f1e8e/attachment-0002.sig>