I might be wrong here but it sounds like a common problem with open files, like most log files.
If you remove a file that is currently open by a process it will not know where to write until you restart the process. Check usage with: # fuser -u filename Try removing contents of file but not file itself: # > filename (same as cp /dev/null filename) /Peter Bonivart --Unix lovers do it in the Sun On Tue, 2003-05-27 at 23:12, Ronan Lucio wrote: > Hello, > > I'd like to make a report about the viruses catched by ClamAV. > So, to do this I tried to read the clamav log file and create > a txt file with the results, but, when I remove the clamd log > file, ClamAV don't create it againg. ClamAV only create a new > log file when I restart it. > > So, If I want to leave the file blank each time I read it, > should I restart clamd? > > It's not so good to an automated process. > > Any tip would be appreciated. > > Thank's > Ronan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
