I've had this problem as well, with the news and mail folders. What I've
noticed is that in both of those folders, the logs are stored as 'news.crit,
mail.warn, etc' and have no .log extension - and I think this is causing
problems, because you'll end up with things like
'mail.info.1.gz.1.gz.2.gz.2.gz.1.gz.1.gz.1.gz.....etc' - this is where the mass
quantities of files comes from. The flaw in this logic is that there are a
couple log files in the /var/log/ directory that DON'T have this problem even
though they don't have a .log extension... [shrug]. Best thing to do I guess is
update the rpm as people have noted.. it's what I'm doing. :]
<EOL>
Tib
On Tue, 30 Jan 2001, Laurent Duperval wrote:
> Hi,
>
> I've noticed that whenever logrotate is run, it can take more than 2 hours
> to complete. It looks like it's doing something fishy. I'm on LM 7.1 and
> this is the ls -lt |head of /var/log:
>
> -rw-r--r-- 1 root root 16497976 Jan 30 13:08 debug.log
> drw------- 2 root root 5914624 Jan 30 13:08 mail/
> -rw------- 1 root root 91056 Jan 30 13:08 messages
> -rw-r--r-- 1 root root 91399 Jan 30 13:08 syslog
> -rw-rw-r-- 1 root utmp 467712 Jan 30 13:07 wtmp
> -rw------- 1 root root 49106 Jan 30 13:01 cron
> -rw-r--r-- 1 root root 504 Jan 30 13:00 daemon.log
> -rw------- 1 root root 77890 Jan 30 13:00 sudo.log
> -rw------- 1 root root 0 Jan 30 12:36 secure
>
> As you can see, the *directory* size of mail' is huge! I'm trying to do a ls
> in that directory and it's been running for 20 minutes with no output yet.
> Any ideas why this is happening?
>
> L
>
>
