Path: utzoo!utstat!helios.physics.utoronto.ca!news-server.csri.toronto.edu!math.lsa.umich.edu!zaphod.mps.ohio-state.edu!ncar!gatech!mcnc!uvaarpa!haven!ni.umd.edu!sayshell.umd.edu!louie
From: louie@sayshell.umd.edu (Louis A. Mamakos)
Newsgroups: news.software.nntp
Subject: Re: Nntpxmit error 0
Message-ID: <1990Dec29.034048.27998@ni.umd.edu>
Date: 29 Dec 90 03:40:48 GMT
References: <1990Dec28.234730.8332@cmcl2.nyu.edu>
Sender: usenet@ni.umd.edu (USENET News System)
Organization: University of Maryland, College Park
Lines: 30
Nntp-Posting-Host: sayshell.umd.edu

In article <1990Dec28.234730.8332@cmcl2.nyu.edu> rosenblg@acf3.nyu.edu (Gary J. Rosenblum) writes:
>i'm running Cnews with the current patchlevel, and nntp 1.5.10;  ever since
>i upgraded to 1.5.10, i see hundreds of the following messages in my log 
>file each night:
>
>Dec 27 03:25:04 localhost nntpxmit[11519]: acf5.nyu.edu xfer: Error 0

<rest deleted>

If you look at your NNTP batch files, you'll also notice some
weirdness going on there too.  We noticed that the last few entries in
the NNTP batches didn't have the message id listed.  I spent *hours*
looking at relaynews, since its the only program that writes batch
files, right?

Wrong.

We had this problem and I finally tracked it down to nntpxmit failing
to transmit a certain class of articles; namely those that had DEL
characters imbedded in the text.  It looks like the check for a -1
return from writing a character to the network was being triggered by
attempting to transmit the DEL character, which was probably being
sign extended.  Error 0 is being reported because, being that no
actual error occurred, errno was still 0.  Nntpxmit then helpfully
re-writes the batch file with the entry of the article in question
stuck at the end.

Grrr...

louie