Newsgroups: news.software.b
Path: utzoo!henry
From: henry@zoo.toronto.edu (Henry Spencer)
Subject: Re: Uncompressed news discarded in C News
Message-ID: <1990Oct3.162212.24528@zoo.toronto.edu>
Organization: U of Toronto Zoology
References: <1990Sep26.205549.14138@idacom.uucp> <1990Oct2.020620.6929@oresoft.com>
Date: Wed, 3 Oct 90 16:22:12 GMT

>In <1990Sep26.205549.14138@idacom.uucp> andrew@idacom.uucp (Andrew Scott) sez:
>:thishost relaynews `bad/654364346' failed, status 1005 (see errlog)

This means *something* is badly wrong, but I'm at a loss to say just what.
You might try running relaynews manually with one of the troublesome batches
as input, and seeing what the shell has to say about that status.  The high
bit indicates that the program is not just returning a non-zero exit status,
it is actually failing by being hit with some sort of signal.  That is Not
Normal, to put it mildly, and we've never seen it before.

>:The strange thing about this is that there is nothing in errlog to indicate
>:what went wrong...

Almost certainly the signal, whatever it is, is blowing relaynews away before
it can get a message out to errlog.

If you are using the stdio speedups we supply, you might try rebuilding
news without them.  It is just possible that there is some very obscure
incompatibility in your stdio that our test doesn't detect.
-- 
Imagine life with OS/360 the standard  | Henry Spencer at U of Toronto Zoology
operating system.  Now think about X.  |  henry@zoo.toronto.edu   utzoo!henry