🚀 go-pugleaf

On Friday, in article <843238776snx@warren.demon.co.uk>
     leveret@warren.demon.co.uk "Nick Leverton" wrote:

NL> On a couple of occasions I've suspected the same thing, that an
NL> immediate socket reset caused the News time to be updated.  However, the
NL> only time I sat down to investigate it, it turned out that there was no
NL> new news because the feed was stalled, and the time was being correctly
NL> updated correctly.  However, I too have had a lingering suspicion that
NL> there was a bug in this area.  If there is, it must be pretty obscure
NL> though.

    I've never experienced this, even though I've reset sockets many 
    times during the worst outbreaks of the Solaris resent packets 
    bug (now apparently fixed).  In most cases, approximately the 
    same number of articles were offered by the server as before the 
    reset.  The only exceptions were when I connected to a different 
    server, which suggests that synchronisation is far from perfect.  
    However, the differences were never major enough to suggest that 
    the time news was last collected had been reset in nntp.dat.
    
    
-- 

"Any news?" "Nope, not a new."
_____________________________________________________________________
Shakib Otaqui                                         Al-Quds Consult