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? Thanks, Michael -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
