It happened again. Third time. /var/log/slim.log grows and grows and I finally get an error that slim.log exceeded the file size. This time I was in x and I lost my wall paper and desktop icons for xfce. I controlled-alt-backspaced out to a prompt and tried to restart and found the error. I then deleted /var/log/slim.log and logged back in with no trouble.

There must be some reason for this. Should the log reset after a predetermined amount of time? Is there a way to do this?

eriefisher

eriefisher wrote: There must be some reason for this.

How about searching the log file for an answer ...

eriefisher wrote: Should the log reset after a predetermined amount of time?

Yep - weekly, as specified in /etc/logrotate.conf as default.

eriefisher wrote: Is there a way to do this?

You could edit /etc/logrotate.d/slim to the effect that slim.log gets rotated daily (- see
========= SCRAPER REMOVED AN EMBEDDED LINK HERE ===========
url was:"http://linux.die.net/man/8/logrotate"
linktext was:"man logrotate"
====================================
for details).

But, again: log files don't"explode" at random ...

Thanks U.R.

Looking at the log it seems to be kde stuff. It look like it's looking for mime types and paths that don't exist. I have a few kde apps so I think it's looking for the kde base stuff. I will have to trace it back.

eriefisher

eriefisher wrote: I will have to trace it back.

Feel free to mail a copy to me to have a second pair of eyes on it __{{emoticon}}__

How about the revision of the logrotate"directive"? Does it work?

I see how logrotate works and I think it will do the trick. I've deleted the log to start fresh and I'm going to follow it and try to correct the issues before I revise logrotate.

Thanks for the offer, I'll let you know.

eriefisher