The process still has an open file handle, and will continue to do so even after you move it. So, if your file is /var/log/messages, and you do a mv /var/log/messages /var/log/messages.old or something (I know that's stupid, but this is an example), the process will continue to write to /var/log/messages.old. The best way is what Chris said: copy the file, and cat /dev/null > logfile. That'll truncate it well. -----Original Message----- From: Ragnar Kj�rstad [mailto:[EMAIL PROTECTED]] What's wrong with moving the file when it's in use? Copying the file will take much longer, and you might loose log-entries that are written after cp but before truncate. -- Ragnar Kjorstad
- Re: [ADMIN] [7.0.2] rotating log files ... Chris Ryan
- Re: [ADMIN] [7.0.2] rotating log files ... Ragnar Kj�rstad
- Re: [ADMIN] [7.0.2] rotating log files ... Dana Hudes
- Re: [ADMIN] [7.0.2] rotating log files ... Alfred Perlstein
- Re: [ADMIN] [7.0.2] rotating log files ... Ragnar Kj�rstad
- Re: [ADMIN] [7.0.2] rotating log files ... Dana Hudes
- Re: [ADMIN] [7.0.2] rotating log files ... Lamar Owen
- Re: [ADMIN] [7.0.2] rotating log files ... Alfred Perlstein
- Re: [ADMIN] [7.0.2] rotating log files ... Palle Girgensohn
- Re: [ADMIN] [7.0.2] rotating log files ... Bruce Momjian
- RE: [ADMIN] [7.0.2] rotating log files ... Neil Toronto
- RE: [ADMIN] [7.0.2] rotating log files ... The Hermit Hacker
- Re: [ADMIN] [7.0.2] rotating log files ... Ragnar Kj�rstad
