Excerpts from Michael Biebl's message of Tue Jul 15 14:55:54 +0200 2014: > On Tue, Jul 15, 2014 at 02:09:18PM +0200, Michal Suchanek wrote: > > 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 > > Please provide the exact list of sysfs keys which are correctly set > after boot and which are not correctly set (and their expected value). > > > Do you have a tool like pm-utils, acpi-support or similar installed, > which might change the sysfs keys after systemd-sysctl.service was run?
ii pm-utils 1.4.1-9 all utilities and scripts for power management ii acpi-support 0.140-5 all scripts for handling many ACPI events However, it has been confirmed that entries unrelated to PM were not set: Excerpts from Craig Small's message of Tue Jul 15 14:23:58 +0200 2014: > > Do you want the status after booting when the variables are not set as well? > I can confirm that the systemd "procps" does not set the variables > correctly. > > # cat /proc/sys/net/ipv6/conf/lo/accept_ra > 1 > # grep accept_ra /etc/sysctl.d/* > /etc/sysctl.d/ipv6-eth0.conf:net.ipv6.conf.lo.accept_ra = 0 > # service procps start > # cat /proc/sys/net/ipv6/conf/lo/accept_ra > 1 > > procps sysctl works: > # sysctl -q --system > # cat /proc/sys/net/ipv6/conf/lo/accept_ra > 0 > > I tried slashes, putting it into /etc/sysctl.conf, removing spaces > around the equals sign. None of them made a difference. > I'm amazed noone else sees this problem. > > What is really strange is running > /lib/systemd/systemd-sysctl > directly works and the parameters change. > So its something after "service procps start" but before > systemd-sysctl is started. > > - Craig Thanks Michal _______________________________________________ Pkg-systemd-maintainers mailing list Pkg-systemd-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers
