[leafnode-list] [ln2] ln2 doesn't clean up out.going

["J. Meyer" <jhmmail@xxxxxx>]

<x-flowed>
Hi,
first run of fetchnews:
Dec 16 18:19:00 gw fetchnews[2050]: found 2 articles in out.going.
Dec 16 18:19:24 gw fetchnews[2050]: found 2 articles in out.going.
Dec 16 18:19:24 gw fetchnews[2050]: Posting 
/var/spool/news/out.going/1658-1040055118-1
Dec 16 18:19:25 gw fetchnews[2050]: Posting 
/var/spool/news/out.going/1895-1040059096-1

next run:
Dec 16 19:45:39 gw fetchnews[6458]: found 2 articles in out.going.
Dec 16 19:45:57 gw fetchnews[6458]: found 2 articles in out.going.
Dec 16 19:45:57 gw fetchnews[6458]: Message-ID of 
/var/spool/news/out.going/1658-1040055118-1 already in use upstream -- 
discarding article
Dec 16 19:45:57 gw fetchnews[6458]: Message-ID of 
/var/spool/news/out.going/1895-1040059096-1 already in use upstream -- 
discarding article

ls /var/spool/news/temp.files/|grep 104005
1658-1040055118-1
1895-1040059096-1
Is this a bug or a feature ("backup" of postings)?

leafnode -V
leafnode 2.0.0.alpha20021108a
Any hints (may be a RTFM)?

TIA

Jochen

--
leafnode-list@xxxxxxxxxxxxxxxxxxxxxxxxxxxx -- mailing list for leafnode
To unsubscribe, send mail with "unsubscribe" in the subject to the list
</x-flowed>