Logging maintenance question

[Gene Heskett]

Greetings all;

I just discovered that some custom scripts I wrote a year or so, seem to have 
gone on the milling list, and that both the fetchmail.log and the 
procmail.log were approaching a gigabyte in size.

So I cobbled up this:
======
# Logrotate file for fetchmail.log and procmail.log
 
/var/log/fetchmail.log {
	missingok
	compress
	notifempty
	weekly
	rotate 5
	create 0600 gene gene
}
/var/log/procmail.log {
        missingok
        compress
        notifempty
        weekly
        rotate 5
        create 0600 gene gene
}
==========
and put it in /etc/logrotate.d with the same perms as most of them there.

But, executing "logrotate -v /etc/logrotate.conf"  returns instantly doing 
nothing to the old logs.  The generated listing of course is detailed and 
includes this:
======
rotating pattern: /var/log/fetchmail.log  weekly (5 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/fetchmail.log
  log does not need rotating

rotating pattern: /var/log/procmail.log  weekly (5 rotations)
empty log files are not rotated, old logs are removed
considering log /var/log/procmail.log
  log does not need rotating
=======
The procmail.log I had just rotated by hand, but do I need to kill fetchmail, 
do it, then restart it?  That log is currently 77 megabytes and several 
months old.

How does one normally go about testing such things?

-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
brokee, n:
	Someone who buys stocks on the advice of a broker.