Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!ihnp4!inuxc!pur-ee!j.cc.purdue.edu!abe
From: abe@j.cc.purdue.edu.UUCP
Newsgroups: comp.unix.questions,comp.unix.wizards
Subject: Re: Tandy XENIX 3.01.02 cron sudden death
Message-ID: <3310@j.cc.purdue.edu>
Date: Thu, 19-Feb-87 09:23:30 EST
Article-I.D.: j.3310
Posted: Thu Feb 19 09:23:30 1987
Date-Received: Sun, 22-Feb-87 15:38:13 EST
References: <124@petro.UUCP> <1337@ncc.UUCP>
Reply-To: abe@j.cc.purdue.edu.UUCP (Vic Abell)
Organization: Purdue University Computing Center
Lines: 9
Keywords: XENIX 3.01.02, cron
Xref: watmath comp.unix.questions:1131 comp.unix.wizards:1074

In article <1337@ncc.UUCP> lyndon@ncc.UUCP (Lyndon Nerenberg) writes:
>I have seen this happen under CTIX as well. It happened on a very
>sporadic basis. No core dumps were found. The only evidence was a
>error return in the accounting logs when cron tried to fork at startup.

One thing to check here: some Bourne shells run out of table space
for &'d processes when executing /etc/rc and fail to start daemons
in an unpredictable fashion.  Inserting a few strategic "wait" calls
in rc can sometimes help.