You are not logged in.
- Topics: Active | Unanswered
#1 2012-03-07 05:02:04
- kdar
- Member
- From: Sweet home Alabama!
- Registered: 2009-06-27
- Posts: 356
settings in sysctl.conf not re-loaded on reboot - kernel.printk
My default kernel.printk values are 15 1 1 7, so I get bunch of kernel messages on all tty shells.
So to fix this, I changed default kernel.printk values from 15 1 1 7 to 4 1 1 7 by modifying line in sysctl.conf > "kernel.prink 4 1 1 7"
When I do sysctl -p, changes get applied and excess kernel message go away. However if I reboot, kernel.prink goes back to 15 1 1 7 and I have to run sysctl -p again.
Offline
#2 2012-03-07 09:42:35
- Gcool
- Member
- Registered: 2011-08-16
- Posts: 1,456
Re: settings in sysctl.conf not re-loaded on reboot - kernel.printk
I've seen this issue reported in a few other threads before (sysctl.conf settings apparently not being applied during boot). Not really sure what's causing it; but you could workaround the issue by adding "sysctl -p" to your /etc/rc.local. Not a structural fix obviously, but it will get rid of the issue.
Burninate!
Offline
#3 2012-03-07 15:21:44
- Leonid.I
- Member
- From: Aethyr
- Registered: 2009-03-22
- Posts: 999
Re: settings in sysctl.conf not re-loaded on reboot - kernel.printk
Can you verify that /etc/rc.multi is run? Because this is where sysctl -p is called. Are other values in sysctl.conf applied correctly on boot?
Having said that, don't you need "=": kernel.printk = a b c d...
Arch Linux is more than just GNU/Linux -- it's an adventure
pkill -9 systemd
Offline