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: mishkin@APOLLO.UUCP (Nathaniel Mishkin)
Newsgroups: mod.computers.apollo
Subject: Re: process name strangeness (mbx_helper)
Message-ID: <8603040448.AA05033@uw-beaver.arpa>
Date: Mon, 3-Mar-86 09:46:57 EST
Article-I.D.: uw-beave.8603040448.AA05033
Posted: Mon Mar  3 09:46:57 1986
Date-Received: Wed, 5-Mar-86 04:08:57 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 21
Approved: apollo@yale-comix.arpa


    This doesn't seem to be very important, but I am curious.  On one
    of our file servers, the mbx_helper process shows up in the 'pst'
    listing as unnamed (i.e., with a UID number).  It is started the
    regular way from startup.spm via a 'cps /sys/mbx/mbx_helper', exactly
    as it is on other servers.  Only on one is it unnamed (of course,
    it doesn't show up in `node_data/proc_dir on that node, but does
    on others).

Sometimes, names get "stuck" -- the name of a previously incarnated process
stays around (in "`node_data/proc_dir") even after the process goes away.
(Typically, the process has to die in a somewhat horrible way for this
problem to arise.) This sometimes prevents NEW processes from using the
same name.  One or both of the following should fix your problem:  (1)
"dlf `node_data/proc_dir/mbx_helper"; (2) reboot your node.

                -- Nat Mishkin
                   Apollo Computer
                   apollo!mishkin

-------