Look at the logrotate system. It can, and should, be set to rotate all logs include the message file either on a set schedule or when the logs exceed a certain size. If it is not happening then logrotate is not running or is experiencing an error. If it is not running, make sure it is set to run in cron. Then check the logrotate.status file to see when various logs were last rotated; if it has been a while then logrotate must be experiencing an error, which in my experience is usually something screwy in the logrotate.status file. If it looks like there is a problem, I try running logrotate interactively so I can see the errors. - rick warner _______________________________________________ Redhat-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/redhat-list
- RE: Samba and win 2000 pr... Thierry ITTY
- Re: Samba and win 2000 pro Mikkel L. Ellertson
- Re: Redhat 7.0 kernal compiling Denis J. Cirulis
- Re: Redhat 7.0 kernal compiling Kapil Sharma
- Re: Redhat 7.0 kernal compiling RaghuNath L
- overly large /var/log/messages jack wallen, jr
- Re: overly large /var/log/messages stewb
- Re: overly large /var/log/messages jack wallen, jr
- Re: overly large /var/log/messages Greg Wright
- Re: overly large /var/log/messages Luke C Gavel
- Re: overly large /var/log/mes... Rick Warner
- Re: overly large /var/log/messages Leonard den Ottolander
- Re: Redhat 7.0 kernal compiling Kapil Sharma
- Re: Redhat 7.0 kernal compiling Inu Wikantiyoso
- Re: Redhat 7.0 kernal compiling Trond Eivind Glomsrød
- Re: Redhat 7.0 kernal compiling Kapil Sharma
- Re: Redhat 7.0 kernal compiling RaghuNath L
- Re: Redhat 7.0 kernal compiling Kapil Sharma
- Re: Redhat 7.0 kernal compiling RaghuNath L
- Re: Redhat 7.0 kernal compiling Kapil Sharma