Newsgroups: news.software.b
Path: utzoo!henry
From: henry@utzoo.uucp (Henry Spencer)
Subject: Re: CNews building up files in "in.coming"
Message-ID: <1989Nov13.190535.2533@utzoo.uucp>
Organization: U of Toronto Zoology
References: <1989Oct22.192159.4827@acd4.UUCP> <1989Oct30.121734.1658@twwells.com> <1989Nov1.184509.27953@utzoo.uucp> <1989Nov13.101830.19896@twwells.com>
Date: Mon, 13 Nov 89 19:05:35 GMT

In article <1989Nov13.101830.19896@twwells.com> bill@twwells.com (T. William Wells) writes:
>: I conjecture that this is a relatively rare situation.  If there are lots
>: of people with such problems, I'd like to hear about them.  (Note, we are
>: talking about major variations over very short time periods:  minutes not
>: hours.) ...
>
>Well, did you get much of a response?

Total silence, I'm afraid.  Looks like you're on your own on this one, Bill,
unless I have a sudden inspiration showing some easy way to deal with it.

>BTW, the things I was thinking of doing, in response to a yes to
>the above, were stuff like deleting each input file after it was
>successfully processed and compressing the backup log and history
>files...

On my current low-priority to-do list (the high-priority list is "dbz")
is to look at changes resembling the last two.  Utzoo, these days, in
fact deletes history.o and compresses log.o when relevant processing
is complete.

You might also want to look at the -s option of expire (and doexpire).
-- 
A bit of tolerance is worth a  |     Henry Spencer at U of Toronto Zoology
megabyte of flaming.           | uunet!attcan!utzoo!henry henry@zoo.toronto.edu