Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
The log rotates properly, creating the previous days log w/ a YYYYMMDD extension (i.e. info.log-20090619). The actual log file (info.log) is empty and not receiving log messages. The latest log file (info.log-20090619) is instead appending with the log messages. I can't figure out why this would be - any ideas?!?!?
I thinke the problem is that when logrotate rotate the file, it creates a new file and simply renames the old one. The old file, thus with the old inode, will still be written to as long as the application doesn't reopen the file. So in other words, as long as the application isn't told otherwise, it will continue to write to the same inode forever.
You can do one of two things: 1) Make sure the application closes and opens connection to the file (this is what the "kill -HUP" signal often is used for), or 2) use the notruncate option (or whatever it it called again) in logrotate.
thanks kenneho - that is something I was looking at.
However, what PID would I kill to effectively restart the service - rsyslog? The external logs are configured thru the rsyslog.conf file. Should I kill the rsyslog PID?
thanks kenneho - that is something I was looking at.
However, what PID would I kill to effectively restart the service - rsyslog? The external logs are configured thru the rsyslog.conf file. Should I kill the rsyslog PID?
I'm going to try the copytruncate command - see how that works...find out tomorrow morning! Thanks again!
Take a look in /etc/logrorate.d/syslog - you've probably allready got a line for rsyslog there. If you need to rotate other logs, you can either enter them there or use the HUP-syntax in another config file.
Shouldn't that be "rsyslogd.pid", and not plain "syslogd.pid"? Btw, you can issue the "logrotate" command with the path to your config file added, to test your setup now. And you can add the "-v" flag and/or "-f" flag if you want to.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.