Linux is dumping tens of gigs of logs every day because the CPU in overheating (I don't care)
Is there a way to stop this crazy logging? It's both inkern.logandsyslog
>>52464336
cool the CPU properly
>>52464364
Not an option. I just want turn off CPU warnings of the kind "WARNING: CPU: 0 PID: 0 at /build/linux..." (and continues with a page of text, repeated infinitely)
>>52464364
a way to redefine "properly" would help, too.
journald.conf
SystemMaxUse=50M
buy a fan
>>52465326
I don't have a 'journald.conf' on my system.
And it would be nicer to stop the logging, because it itself uses resources.
>>52464336
ln -s /dev/null kern.log
do the same for syslog
>>52465757
Thanks, I'll do it as a last resort. If there are no better options...
>>52464336
>tens of gigs
wew
but um
buy a fan and put the fan on the cpu
uninstall syslogd and other stuff (i got it down to just dmesg)
It just werks
>>52466319
for now I commented out these tow guys in /etc/rsyslog.conf
>#$ModLoad imuxsock # provides support for local system logging
>#$ModLoad imklog # provides kernel logging support
the logging seems to have stopped
Fix your CPU, nigger.
kill yourself
>>52465662
he expected you to have systemd, what kind of a linux user are you if you don't have systemd as PID1
>>52467990
PID1 is /sbin/init
rsyslogd does the logging
>>52464336
maybe you could use sed in root's crontab
something like@hourly sed -i.bak '/"WARNING: CPU: 0 PID: 0 "/d' /var/log/kern.log
>>52468142@hourly sed -i.bak '/WARNING: CPU: 0 PID: 0 /d' /var/log/kern.log
i always forget about sed's syntax . this will werk
>>52464336
hahahha, that caption