syslogd quits at 2GB
I have a log file server running Slackware 9.1. I am having difficulty with syslogd... whenever any one of the log files reaches 2GB in size, syslogd stops and its process is killed. If I try to restart syslogd with the -d option, I get the message "File size limit exceeded". If I delete the 2GB log file, syslogd starts up fine.
When syslogd fails, ps confirms its process is not running and netstat confirms UDP 514 is not listening. I am using the reiser file system and there is plenty of room in the /var partition. I can create files myself that are greater than 2GB in size by continually "cat >>" data to a file, so I don't think it's a filesystem issue. Any suggestions? |
you can use logrotate to rotate and compress your logs regularly so you never reach the 2GB limit. ext2 had the 2GB limit on files. So, perhaps syslogd has a safety feature that shuts it down at the 2GB limit .... I may be wrong here.
|
All times are GMT -5. The time now is 01:55 AM. |