Behaviour of nnrpd during expire
Alex Kiernan
alexk at demon.net
Mon Feb 12 17:34:11 UTC 2001
I'm more or less there on hauling all of the non-expire history code
out into the proposed API, but I've just hit nnrpd.
nnrpd goes to some efforts to make sure its using the current history
file following a swap over during expire; I could hide this inside
HISlookup, with a timeout of say 30s between stats - anyone got any
better ideas?
innd doesn't suffer from this because it knows to close/open the
history.
--
Alex Kiernan, Principal Engineer, Development, Thus PLC
More information about the inn-workers
mailing list