Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!apollo
From: holtz%cascade.carleton.cdn%ubc.CSNET@CSNET-RELAY.ARPA (Neal Holtz)
Newsgroups: mod.computers.apollo
Subject: Re: process name strangeness (mbx_helper)
Message-ID: <434:holtz@cascade.carleton.cdn>
Date: Mon, 3-Mar-86 20:58:33 EST
Article-I.D.: cascade.434:holtz
Posted: Mon Mar  3 20:58:33 1986
Date-Received: Wed, 5-Mar-86 04:07:35 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 13
Approved: apollo@yale-comix.arpa

Actually, I suspect I have the answer to why mbx_helper was unnamed,
and it wasn't very important.  'startup.spm' had the line 
'cps /sys/mbx/mbx_helper' in it, but when I was watching the diagnostics
on a CRT attached to the DSP-80 during boot, I noticed the message at the
end of the boot process that said:
     "MBX_HELPER not running. Starting one"
I bet that 2 copies of mbx_helper got started, the first one died
after having named itself, and the second (unnamed one) continued.

I removed the "cps ..." command from the startup file; at the next crash
(shouldn't be long) we will see if that was the problem.

Is this right?  Seems a little strange.