Just to say me too.
Noticed this some time (ie months) ago in the 2.4 series, haven't had
time to track it down but had assumed it was likely to be my setup due
to lack of anyone else shouting.
Traced it down to active file not being updated resulting in inn getting
it's hi-lo item nos totally screwed on a restart. Often resulted in new
items being assigned nos for items that already existed and big holes in
nos when a renumber was run at expire time.
Quick hacky workaround by running ctlinnd renumber "" after each start of
rc.news. This isn't a fix - my active file hasn't been updated since 6/8.
Running inn 2.2.3.
Mike
-- Mike Civil Home : mike@duncodin.org Broadmayne, Dorset, UK Work : Mike.Civil@barclays.co.uk +44 (0)1305 853644- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Tue Aug 15 2000 - 21:00:28 EST