irritating arugs behaviour

[Carter Bullard]

Hey Russell,
I'm thinking about this and trying to come up with a reasonable
solution to your problem.  Understanding that there is not enough
diskspace is tricky unless you generate a filesystem full error, and
I'm wondering if there isn't something a little more elegant.

I'll ponder this until tomorrow, and lets figure out what we need to do.

I was very glad to see that the program "arugs" was irritating you
instead of my program.

Carter

On Sep 24, 2007, at 5:18 PM, Russell Fulton wrote:

> Hi
>
> When a disk write from argus fails (due to diskfull for example) argus
> keeps running but never retries the output file.   I have a daily job
> that clears space in the archive and occasionally the cleared space is
> not enough for the next day's logs so the system runs out of disk late
> at night.
>
> I've just got  back after a few days away to find that the monitor ran
> out of disk on the first evening, of course!  :)
>
> When argus closes an output process due to errors it would be nice  
> if it
> could recheck the file periodically to see if it can proceed again.
>
> Some time in the not too distant future I will move to using radium on
> the central controller where I will have much more disk but in the  
> mean
> time it would be nice if argus could retry blocked output processes  
> say
> every 15 minutes.
>
> Russell
>
>
>