[news at gallifrey.nk.ca: gallifrey.nk.ca daily usenet report for Sun Mar 5 01:00:00 MST 2006]

[Russ Allbery]

The Doctor <doctor at doctor.nl2k.ab.ca> writes:

> Looks as if expire might have a potential bug.

I'm not sure what you're looking at.  I see a bunch of error messages from
uux in your error log, but that doesn't have anything to do with expire.

> Error log:
> 20060304053906.0573 uux: error -- Bad system name: thwap
> 20060304053906.0573 uux: ERROR -- node thwap, code 68
> 20060304061801.0064 uux: error -- Bad system name: thwap
> 20060304061801.0072 uux: ERROR -- node thwap, code 68
> 20060304061839.0996 uux: error -- Bad system name: thwap
> 20060304061839.0997 uux: ERROR -- node thwap, code 68
> overchan: timings 30406 arts 117909 of 42213719 ms
> overchan: timings 3 arts 59 of 8488 ms
> overchan: timings 1 arts 0 of 7818 ms
> 20060304194702.0020 uux: error -- Bad system name: thwap
> 20060304194702.0039 uux: ERROR -- node thwap, code 68
> batcher: thwap batch 1 exit status 17408

Also, it looks like expire didn't run because it thought it was already
running:

> ctlinnd: Reserved "Expiring process 13336"

-- 
Russ Allbery (rra at stanford.edu)             <http://www.eyrie.org/~eagle/>

    Please send questions to the list rather than mailing me directly.
     <http://www.eyrie.org/~eagle/faqs/questions.html> explains why.