Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watnot!watmath!clyde!rutgers!husc6!wjh12!maynard!campbell
From: campbell@maynard.UUCP
Newsgroups: news.software.b
Subject: Re: Problem with News 2.11.6 and fix
Message-ID: <882@maynard.BSW.COM>
Date: Sat, 28-Mar-87 08:05:14 EST
Article-I.D.: maynard.882
Posted: Sat Mar 28 08:05:14 1987
Date-Received: Sun, 29-Mar-87 09:05:01 EST
References: <199@ems.UUCP>
Reply-To: campbell@maynard.UUCP (Larry Campbell)
Organization: The Boston Software Works, Inc.
Lines: 31
Summary: your diagnosis is wrong

In article <199@ems.UUCP> mark@ems.UUCP (Mark H. Colburn) writes:
]...
]Looking up a couple lines of code, the code to fork off the child process
]reads:
]
]			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).

No, this means the child will exit with a code of 1 if the execl fails.
If the execl succees, the "_exit(1);" is obviously never reached.
-- 
Larry Campbell                                The Boston Software Works, Inc.
Internet: campbell@maynard.BSW.COM          120 Fulton Street, Boston MA 02109
uucp: {alliant,think,wjh12}!maynard!campbell        +1 617 367 6846