Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!linus!gatech!gt-karloff!spaf
From: spaf@gt-karloff.UUCP
Newsgroups: news.software.b
Subject: Re: Problem with News 2.11.6 and fix
Message-ID: <14325@gatech.edu>
Date: Fri, 27-Mar-87 12:59:10 EST
Article-I.D.: gatech.14325
Posted: Fri Mar 27 12:59:10 1987
Date-Received: Sat, 28-Mar-87 13:42:55 EST
References: <199@ems.UUCP>
Sender: news@gatech.edu
Reply-To: spaf@gt-karloff.UUCP (Gene Spafford)
Organization: Software Engineering Research Center (SERC), Georgia Tech
Lines: 34
Keywords: Hmmmm...

In article <199@ems.UUCP> mark@ems.UUCP (Mark H. Colburn) writes:
 > ...
 >
 >			if ((pid=vfork()) == -1)
 >				xerror("Can't fork: %s", errmsg(errno));
 >			if (pid == 0) {
 >#ifdef IHCC
 >				char bufr[BUFSIZ];
 >				sprintf(bufr, "%s/%s", logdir(HOME), RNEWS);
 >				execl(bufr, "rnews", "-S", "-p", dir->d_name,
 >					(char *) NULL);
 >#else /* !IHCC */
 >				execl(RNEWS, "rnews", "-S", "-p", dir->d_name,
 >					(char *) NULL);
 >#endif /* !IHCC */
 >				_exit(1);
 >				^^^^^^^^^
 >This means that the child will _ALWAYS_ exit with a code of 1, and the 
 >parent will _ALWAYS_ abort with an error of 256.  Obviously the fix is to 
 >modify the _exit(1) to an _exit(0).

That is *NOT* the fix, since that is *NOT* the problem.  That exit
is executed ONLY if the preceding "execl" fails.  That is cause for
error and exactly the reason you want to exit with a non-zero error
code.  If the execl succeeds (overlaying the memory image with
a new version of rnews), the error value returned is the exit
status of that new image of rnews.

You need to look further for the cause of your problem.  Have you
looked in the "errlog" file for messages?
Gene Spafford
Software Engineering Research Center (SERC), Georgia Tech, Atlanta GA 30332
CSNet:	Spaf @ GATech		ARPA:	Spaf@Gatech.EDU
uucp:	...!{akgua,decvax,hplabs,ihnp4,linus,seismo,ulysses}!gatech!spaf