Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!samsung!umich!terminator!pisa.ifs.umich.edu!rees
From: rees@pisa.ifs.umich.edu (Jim Rees)
Newsgroups: comp.sys.apollo
Subject: Re: Why do I need a "sfcb hash table mutex lock"?
Message-ID: <4f1642f4.1bc5b@pisa.ifs.umich.edu>
Date: 8 Jan 91 18:59:03 GMT
References: <9012280914.AA03633@duc220.uni-duisburg.de> <1990Dec30.194240.17416@alphalpha.com> <4ef7cdb8.1bc5b@pisa.ifs.umich.edu> <1991Jan3.202230.12597@alphalpha.com>
Sender: usenet@terminator.cc.umich.edu (usenet news)
Reply-To: rees@citi.umich.edu (Jim Rees)
Organization: University of Michigan IFS Project
Lines: 13

In article <1991Jan3.202230.12597@alphalpha.com>, nazgul@alphalpha.com (Kee Hinckley) writes:
  In article <4ef7cdb8.1bc5b@pisa.ifs.umich.edu> rees@citi.umich.edu (Jim Rees) writes:
  >...  This won't work any more because reboot() no longer does a shutdown,
  >it signals process 1 to do the shutdown (why was this changed?).
  
  You might try calling reboot(RB_AUTOBOOT).  Unless that was changed too.

That was changed too.  All flavors of reboot() now signal process 1.  If it
doesn't exist (!) or doesn't respond in two minutes, reboot() goes ahead and
tries to shut down in the current process by calling os_$shutdown().

reboot() also sends all processes a SIGTERM, and, if that doesn't work, a
SIGKILL.