Resync groups after server lost time

[Tommy.Fallsen at kongsberg.com]

>> Our news server stopped getting new posts during the=20
>vaction. Checking=20
>> =3D
>> it had the date July 22, so i set it=3D20
>> to the correct date. And i see the news post started comming=20
>in again.
>>
>> But i there is a hole between July 22 and August 8. Can that be=20
>> fixed?=3D20
>
>Not as easily as you'd like.
>
>The trouble is that, while the time was incorrect, your server=20
>rejected=20
>all of those missing posts.  In doing so, it recorded their=20
>Message-IDs=20
>in the history database, and will refuse to reexamine them if offered=20
>again.
>
>So if you want to fill in the hole, you need to (1) remove the bad=20
>entries from the history database, and (2) offer the articles to your=20
>INN again.
>
>It looks like you were working on #2 (although I'm not familiar enough=20
>with nntpget to comment on the details).
>
>You still have to do #1, though.  There are a few possibilities, none=20
>wonderful...
>
>- you can wait for the /remember/ time in expire.ctl to pass
>
>- you can adjust the /remember/ time in expire.ctl, wait for it to=20
>pass, and then restore it (if you make it too short, you may get=20
>duplicates on your server)
Its set too 60, can i set to to 3 and restart inn? since it got articles =
from the last two days.

>
>- you can get a list of all the Message-IDs for missing articles, and=20
>remove them from the history database manually (rebuilding with=20
>makedbz) afterwards
How do i do this?


Tommy