LIST commands
Julien ÉLIE
julien at trigofacile.com
Tue Dec 23 14:06:43 UTC 2008
Hi Matija,
>> Ideally, inncheck should also check those files for any invalid lines so
>> that the administrator has a chance to learn about them and fix them.
>
> I would've even prefer putting such logic ONLY in inncheck (duplicating same
> logic in two places is IMHO not a good idea, as they will drift away one
> from another with time)
It sounds OK to me.
> It would also be good idea to make inncheck run periodically (at least from
> news.daily?) and mail any output to news administrator.
Is it all right to put the result at the beginning of the daily Usenet mail
report?
inncheck -a -pedantic
should be enough. Permissions checking could be wrong (if owned by other groups,
like uucp).
There is also #70 to deal with:
http://inn.eyrie.org/trac/ticket/70
"I wish it was easier to spot in the news.daily report that the expire didn't
work because I buggered up the expire.ctl file. Ideally, information like errors
should be right at the top of the file, not way down below the boring stuff
about how many articles I sent to eachone of my peers and the like."
However, I do not see well how to find out errors during expire. They are just
written in the expire part. Should we "grep -v" known lines and put the result
at the beginning of the report?
--
Julien ÉLIE
« When a man opens the door of his car for his wife,
you can be sure of one thing: either the car is new or the wife. »
More information about the inn-workers
mailing list