From: Robert Bannocks APL UNIX System Manager (robert@apl.ucl.ac.uk)
Date: Mon Jul 29 2002 - 14:21:24 EDT
Thanks go to
"A. Mahendra Rajah" <Mahendra.Rajah@URegina.CA>
Stan Horwitz <stan@temple.edu>
"Lavelle, Bryan" <Bryan.Lavelle@hp.com>
"Brown, Tony" <TBrown2@nmff.org>
Peyton Bland <bland@umich.edu>
Oisin McGuinness <oisin@sbcm.com>
From: "Dr Thomas.Blinn@HP.com" <tpb@doctor.zk3.dec.com>
From: mcaplin@miami.edu
for replying.
mcaplin@miami.edu, "Dr Thomas.Blinn@HP.com" <tpb@doctor.zk3.dec.com>,
Oisin McGuinness <oisin@sbcm.com> and "A. Mahendra Rajah" <Mahendra.Rajah@URegina.CA>
found the answer. some how the boot_osflags had got reset. Their answers
are given below.
> I have a problem with a just installed Tur64 system (Tru64 v5.1). I have
> done something to this machine that causes it to halt in single user
> mode when ever it boots. This is particularly unfortunate as it
> gives the user a root shell. I have to hit CTRL-D to continue the boot.
> The initdefault in /etc/inittab is 3. This appeared
> to happen after it did an aborted kernel rebuld. I have searched the archives
> but can find nothing relevant.
Look at your SRM environment. Check the boot flags, to boot into
multiusers mode, set to "-A", to boot single user (as a default), leave is
empty.
_______________________________________________________________________________
From: "O'Brien, Pat" <pobrien@mitidata.com>
srm variable "boot_osfalgs =0 or s" or boot -fl or -flag =0 or s will do the
same
> Rob
Check your "boot_osflags" console variable. If it's not set or is set
to "s", you'll see what you're seeing. Setting it to "a" usually gets
the system to come all the way up to multi user mode. Depending on the
system model, you may be able to set the flag with the "consvar" root
command (see the reference page). However, on some system models (my
AlphaPC 164/LX is one), you can't use that command to set variables.
In that case, next time you have halted the system, use the console's
commands to set the variable to "a", then do an "init" and reboot.
Tom
Dr. Thomas P. Blinn + Tru64 UNIX Software + Hewlett-Packard Company
Internet: tpb@zk3.dec.com, thomas.blinn@compaq.com, thomas.blinn@hp.com
110 Spit Brook Road, MS ZKO3-2/W17 Nashua, New Hampshire 03062-2698
Technology Partnership Engineering Phone: (603) 884-0646
ACM Member: tpblinn@acm.org PC@Home: tom@felines.mv.net
From: "Dr Thomas.Blinn@HP.com" <tpb@doctor.zk3.dec.com>
X-Mts: smtp
Status: O
From: Oisin McGuinness <oisin@sbcm.com>
The console variable boot_os_flags is probably empty; set it to "A".
>>> set boot_os_flags A
Check to see that boot_osflags is set to A or a at the console level.
From: "A. Mahendra Rajah" <Mahendra.Rajah@URegina.CA>
"it to halt in single user mode when ever it boots."
Can you type show boot_osflags at the >>> prompt? Does it say
S (single user) or A (multi-user)? If it is S, please change it
This archive was generated by hypermail 2.1.7 : Sat Apr 12 2008 - 10:48:47 EDT