Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!umd5!ames!ptsfa!ihnp4!occrsh!occrsh.ATT.COM!rjd
From: rjd@occrsh.ATT.COM
Newsgroups: comp.sys.att
Subject: Re: 3B2 won't go to init 1.  Help.
Message-ID: <144800011@occrsh.ATT.COM>
Date: 11 Jan 88 14:27:00 GMT
References: <69@mybest.UUCP>
Lines: 31
Nf-ID: #R:mybest.UUCP:-6900:occrsh.ATT.COM:144800011:000:1481
Nf-From: occrsh.ATT.COM!rjd    Jan 11 08:27:00 1988


>A 3B2/310 (at System V release 3.0) that I do some work for
>decided it doesn't want to go to single user.  When instructed to
>go single user, either via init 1 or shutdown -y -g0 -i1 or the equivalent
>using init S or s, it goes into a loop where it asks me what run state I
>want to go to.  
>This simulates the normal response when EOF is typed in single user mode.
>I have tried changing consoles devices, going to single user from different
>ports and deleting /etc/ioctl.syscon.  I guess I think I ought to figure it 
>out, but the cycle time up to multi-user and back is too long to be fun.
>I have not been brave enough to change the inittab line that specifies which
>run state to go to on boot, and I don't particularly want to undertake the
>"standard hotline" solution of a partial restore.
>Suggestions, or better still, solutions welcome.
>
>Steve

  I tried mailing this, but no dice....

Steve,
  One quick fix that might work is to simply "touch /etc/system".  Doing this
will make the /etc/system access time newer than the /unix access time, thus
telling the system to re"make" /unix on the next boot.  (The command used by
the system is 'mkunix' as found in the sysadm manual).  After the touch, do a
reboot ("shutdown -i6 -g0 -y").

  Two or three things can cause this message, a few of which will be fixed
by letting the system remake /unix.  If not, e-mail me and I will see what I
can do.

Randy Davis                     		UUCP: ...(ihnp4!)3b2fst!randy