/var/log/kdm.log file now 7.3GB HELP
in [Suse]
|
Prev: KDE 4.3.4 vs 4.3.1?
Next: Find Syntax Question [CLI]
From: gb on 24 Dec 2009 09:03 Using 11.2 with KDE 4.3.1. I did a clean install of 11.2 about three weeks ago. I noticed my root folder has expanded rapidly and have tracked this down to the /var/log/kdm.log file, which is now 7.3GB in size. Every time I try to open the file the editor crashes. What is in it? Can it be deleted? How can I stop it growing so fast in future? Thanks Geoff Beale
From: Rob on 24 Dec 2009 09:31 gb <gb(a)gb.com.invalid> wrote: > Using 11.2 with KDE 4.3.1. > I did a clean install of 11.2 about three weeks ago. I noticed > my root folder has expanded rapidly and have tracked this down to > the /var/log/kdm.log file, which is now 7.3GB in size. > > Every time I try to open the file the editor crashes. What is in > it? Can it be deleted? How can I stop it growing so fast in > future? This is not normal. To know what is written to this file, try this: tail -200 /var/log/kdm.log This shows you the last 200 lines of the file. Try to fix whatever is going wrong there.
From: David Bolt on 24 Dec 2009 09:52 On Thursday 24 Dec 2009 14:03, while playing with a tin of spray paint, gb painted this mural: > Using 11.2 with KDE 4.3.1. > I did a clean install of 11.2 about three weeks ago. I noticed > my root folder has expanded rapidly and have tracked this down to > the /var/log/kdm.log file, which is now 7.3GB in size. > > Every time I try to open the file the editor crashes. I'm not surprised. You're doing the equivalent of trying to get 1 gallon into a 4 pint bottle. It won't work and, after a while trying, it gives up. > What is in > it? Open a console and type: less /var/log/kdm.log > Can it be deleted? Yes, but you'll need to drop into runlevel 3 and then back to runlevel 5 to really get rid of it. You can do that by logging out from your desktop, pressing ALT-CTRL-F2 and logging in as root. Then enter the command: init 3 ; sleep 5 ; init 5 ; exit This will swap into runlevel 3, pause for 5 seconds, swap back to runlevel 5 and log out. This will make sure the deleted file is closed and properly removed. The "exit" is there so you don't leave root logged in at a console. > How can I stop it growing so fast in > future? Look at it and see why it's growing in the first place. Mine only grows when I restart kdm, which only happens when I log out and update KDE or the kernel. Other than that, it's up and running 24/7. Regards, David Bolt -- Team Acorn: www.distributed.net OGR-NG @ ~100Mnodes RC5-72 @ ~1Mkeys/s openSUSE 11.0 32b | | openSUSE 11.2 32b | openSUSE 11.0 64b | openSUSE 11.1 64b | openSUSE 11.2 64b | TOS 4.02 | openSUSE 11.1 PPC | RISC OS 4.02 | RISC OS 3.11
From: Casperius on 24 Dec 2009 13:41 On 12/24/2009 03:03 PM, gb wrote: > Using 11.2 with KDE 4.3.1. > I did a clean install of 11.2 about three weeks ago. I noticed > my root folder has expanded rapidly and have tracked this down to > the /var/log/kdm.log file, which is now 7.3GB in size. > > Every time I try to open the file the editor crashes. What is in > it? Can it be deleted? How can I stop it growing so fast in > future? > > Thanks > Geoff Beale > my kdm.log is 44.5KiB and I restart and power down my pc every day
From: Moe Trin on 24 Dec 2009 16:09
On Thu, 24 Dec 2009, in the Usenet newsgroup alt.os.linux.suse, in article <slrnhj6uij.deu.houghi(a)penne.houghi>, houghi wrote: >gb wrote: >> Every time I try to open the file the editor crashes. As others have suggested 'tail -200 /var/log/kdm.log' >> Can it be deleted? How can I stop it growing so fast in future? You'll have to find what is filling it up - that rate (7 gigs in 3 weeks) isn't normal. As for limiting it in size, there should be a cron job that monitors the logs and rotates them. >Use vim (or vim if you have it installed) and look whit that. Assumes knowledge of vi or it's many clones - not very likely. 'vim' normally creates a copy of the file (.$FILENAME~) when editing, and there may not be enough space on the hard disk to do so. >If that does not work do (as root or wiith sudo) `mv /var/log/kdm.log >/var/log/kdm.log.bak` and the new file should be much smaller. Yes - it will remain at zero size because the logging daemon is still writing to the original file until that application is restarted. >Could be that you first need to do `touch /var/log/kdm.log`, >although it _should_ create a new file if needed. Only if the daemon is restarted. Why isn't the log rotation cron task handling this? Old guy |