Xref: utzoo comp.unix.wizards:22493 comp.sys.ncr:360
Path: utzoo!attcan!uunet!cs.utexas.edu!asuvax!anasaz!chad
From: chad@anasaz.UUCP (Chad R. Larson)
Newsgroups: comp.unix.wizards,comp.sys.ncr
Subject: Re: Init S on System V 3.2
Message-ID: <2462@anasaz.UUCP>
Date: 15 Jun 90 05:18:21 GMT
References: <1990Jun11.064652.2434@hawkmoon.MN.ORG>
Reply-To: chad@anasaz.UUCP (Chad R. Larson)
Followup-To: comp.unix.wizards
Organization: Anasazi, Inc.
Lines: 26

In article <1990Jun11.064652.2434@hawkmoon.MN.ORG> det@hawkmoon.MN.ORG
 (Derek E. Terveer) writes:
+---------------
| 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.
+---------------
Unless, of course, you're on an NCR Tower running their distribution of
SysVr3.  Then run state 1 is multi-user mode!  Doncha just love the way
people REALLY BELIEVE in standards?  I've got about a half dozen Unix
machines to administer, and I just love it when my fingers (running
ahead of my brain) type something like "telinit 2" when it should have
been "telinit 1" (but only on this one machine....)
	-crl

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


-- 
Chad R. Larson          ...{mcdphx,asuvax}!anasaz!chad or chad@anasaz.UUCP
Anasazi, Inc. - 7500 North Dreamy Draw Drive, Suite 120, Phoenix, Az 85020
(602) 870-3330            "I read the news today, oh boy!"  -- John Lennon