🚀 go-pugleaf

In article <1992Oct13.125400.25341@dickens.com> lpc@dickens.com (Luis P Caamano) writes:
>>I got this message from cnews this morning.  I got an identical
>>one on Saturday.  After looking at the batch file I found that
>>there were a few more characters in an article than what the 
>>#! rnews n line said.  I ignored the error and removed the batch
>>file from in.coming/bad.
>>
>>I got this one again and now I'm wondering if it's a problem with
>>our cnews or it's with uunet.
>>
>>any hints?
>>
>>Forwarded message:
>>> From root Tue Oct 13 08:20:05 1992
>>> Date: Tue, 13 Oct 1992 08:18:28 -0400
>>> From: news@ddssuprs (News Administrator User)
>>> Message-Id: <9210131218.AA25157@ddssuprs>
>>> Organization: Dickens Data Systems, Inc.
>>> To: usenet@ddssuprs
>>> 
>>> 
>>> errlog.o
>>> ---------
>>> relaynews: unbatcher out of synch, tossing: 
>>> relaynews: unbatcher out of synch, tossing: w-
>>> ---------
>>> 
>>> 

Here is what I got:

>
>From: uunet!operator (UUNET Operator)
>Message-Id: <9210131522.AA19035@rodan.UU.NET>
>Subject: Re: unbatcher problem?
>To: lpc@ddssuprs
>Date: Tue, 13 Oct 92 11:22:15 EDT
>In-Reply-To: <9210131252.AA08866@ddseng>; from "Luis P Caamano" at Oct 13, 92 8:
>52 am
>X-Mailer: ELM [version 2.3 PL10]
>Status: RO
>
>> From ddssuprs!lpc Tue Oct 13 09:42:22 1992
>> 
>> I got this message from cnews this morning.  I got an identical
>> one on Saturday.  After looking at the batch file I found that
>> there were a few more characters in an article than what the 
>> #! rnews n line said.  I ignored the error and removed the batch
>> file from in.coming/bad.
>> 
>> I got this one again and now I'm wondering if it's a problem with
>> our cnews or it's with uunet.
>
>It might just be a spurious problem with your line.  I can't see any
>reason why it would be a problem with our batching (and we'd have
>800 other sites complaining if it were).  Even a dollop of line
>noise adding or deleting a character in the batch will cause
>the problem.  It should be possible to remove the offending 
>section (article) and let the rest of the batch through rnews
>so you don't lose anything.
>
>David Lawrence                                  uunet newsmaster
>
>
>From: uunet!operator (UUNET Operator)
>Message-Id: <9210141248.AA00673@rodan.UU.NET>
>Subject: Re: unbatcher problem?
>To: lpc@ddssuprs
>Date: Wed, 14 Oct 92 8:48:38 EDT
>In-Reply-To: <9210131826.AA07717@ddseng>; from "Luis P Caamano" at Oct 13, 92 2:
>26 pm
>X-Mailer: ELM [version 2.3 PL10]
>Status: RO
>
>> From ddssuprs!lpc Tue Oct 13 17:42:52 1992
>> > 
>> > It might just be a spurious problem with your line.  I can't see any
>> > reason why it would be a problem with our batching (and we'd have
>> > 800 other sites complaining if it were).  Even a dollop of line
>> > noise adding or deleting a character in the batch will cause
>> 
>> uhmm, I don't agree.  We get compressed batching, and thus we get 
>> a .Z file which when uncompressed turns into the batch file in
>> question.  The characters were there when the file was compressed
>> and that was done at UUNET.  Or could it be that I got some 
>> garbage as part of the .Z file, nahhh, uucp protocol eliminates
>> that. 
>
>No, uucp protocol does not necessarily eliminate that.  I very, very
>much doubt that the problem was there when the file was compressed at
>UUNET.  Our batchers whines when it finds more characters in an article
>than what it wrote as the #! rnews line, so at least before the batch
>was piped to compress then to uux it was fine.  There is no reason
>to believe that spurious characters were introduced in the pipeline.
>
>
>> > the problem.  It should be possible to remove the offending 
>> > section (article) and let the rest of the batch through rnews
>> > so you don't lose anything.
>> > 
>> 
>> I thought that relaynews kept reading lines until getting back
>> in sync, that is finding the next #!rnews n line.  But I've been
>> wrong before ... :-)
>> 
>> Can you clarify please? 
>
>Nope, you're right.  Momentary brain cloud on my part.
>
>David Lawrence                                          uunet newsmaster
>
>Date: Tue, 13 Oct 92 21:55:24 EDT
>From: uunet!evb.com!mahesh (B.G. Mahesh)
>Message-Id: <9210140155.AA07467@gadget.evb.com>
>To: lpc@dickens.com
>Subject: Re: unbatcher out of sync
>Newsgroups: uunet.forum
>In-Reply-To: <1992Oct13.125400.25341@dickens.com>
>Organization: SETT Inc.
>Cc: 
>Status: RO
>
>Could you summarise it for me? I had the same problem last
>week. UUNET administrators asked me to post it on
>news.software.b. So far I have not heard from that group.
>
>thanks
>
>
>-- 
>
>B.G. Mahesh
>mahesh@evb.com
>
-- 
Luis P. Caamano                        |         lpc@dickens.com
Dickens Data Systems, Inc. Atlanta, GA |         uunet!dickens.com!lpc
---------------------------------------------------------------------------
If I think I know it all, I'll stop learning. -myself
The more I learn, the more I know I know nothing. -somebody else

>>
>>It might just be a spurious problem with your line.  I can't see any
>>reason why it would be a problem with our batching (and we'd have
>>800 other sites complaining if it were).  Even a dollop of line
>>noise adding or deleting a character in the batch will cause
>>the problem.  It should be possible to remove the offending 
>>section (article) and let the rest of the batch through rnews
>>so you don't lose anything.
>>
>>David Lawrence                                  uunet newsmaster
>>

Well., I did try to edit that batch but it has lot of
special characters (like a binary file). The first few lines
look fine (like an ascii file) but as I scroll down further
it is all junk.


-- 

B.G. Mahesh
mahesh@evb.com