Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!terminator!pisa.citi.umich.edu!rees
From: rees@pisa.citi.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: inetd dying during exec()
Message-ID: <5021316a.1bc5b@pisa.citi.umich.edu>
Date: 2 Mar 91 20:57:44 GMT
References: <HANCHE.91Feb28201637@hufsa.imf.unit.no>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan ITD
Lines: 16

In article <HANCHE.91Feb28201637@hufsa.imf.unit.no>, hanche@imf.unit.no (Harald Hanche-Olsen) writes:

  Status         03010002: process had a fatal error (process manager/process manager)
  In routine     "/sys/node_data.a0b0/systmp/global_readonly" offset 363A
  Called from    "pgm_$exec_uid_pn" line 1450
  Called from    "pgm_$exec_xoid_pn" line 1287

This happens when an exec fails after the process is unrecoverably committed
to running the new program.  Since it can't get back to the original program
at this point, the process just exits.  This "shouldn't happen" (be glad
it's not a kernel panic).

  I love that status code!  So informative...

Me too.  Sounds like what you'd say when your three-year-old accidentally
pees on the carpet.