Path: utzoo!attcan!uunet!cs.utexas.edu!uwm.edu!uwvax!umn-d-ub!cs.umn.edu!atc!hawkmoon!det
From: det@hawkmoon.MN.ORG (Derek E. Terveer)
Newsgroups: comp.unix.wizards
Subject: Re: Init S on System V 3.2
Message-ID: <1990Jun11.064652.2434@hawkmoon.MN.ORG>
Date: 11 Jun 90 06:46:52 GMT
Organization: Home System (One of the Eternal Champions)
Lines: 14

In article <1990Jun8.025421.25366@cbnewsl.att.com> sar0@cbnewsl.att.com (stephen.a.rago) writes:
> Use init 0, instead of init s, but you'll have to remount the file
> systems if you need access to them.  Init state 0 will kill the
> processes.  [..]

Hmmm, don't you mean "init 1" here?  "init 0" on most systems (but not all!)
i've seen (but all of the V3.2 systems 'fur sure) will bring the system to a
halt.  This is supposed to be the "about to be powered down state".  Init 1
will do the same as init s except kill superfluous processes and unmount excess
file systems.

derek
-- 
Derek Terveer		det@hawkmoon.MN.ORG