Init S on System V 3.2

Derek E. Terveer det at hawkmoon.MN.ORG
Mon Jun 11 16:46:52 AEST 1990


In article <1990Jun8.025421.25366 at cbnewsl.att.com> sar0 at 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 at hawkmoon.MN.ORG



More information about the Comp.unix.wizards mailing list