SUMMARY: Promiscuous Single Inits

From: Andrew Lamb (
Date: Wed Dec 11 1996 - 17:27:37 CST

        1 Respondants
        2 Advice
        3 Solution Adopted
        4 Original Posting

1 Respondants

Kenn Owen <>
Brian T. Wightman <>
Rick Kelly <>
Phil Poole <>
Stephen P Richardson <>
Karl E. Vogel <>
Benjamin Cline <>
Glenn Satchell <>

2 Advice

        1 ifconfig le0 down (1x)

What I do is leave the machine in multiuser mode, warn everyone that the system
is going down .... then as root I just do: ifconfig le0 (or whatever your
interface is) down. Apply my patches or whatever and when thats done just do a
reboot and the system will come back up in multiuser with the interface up and

        2 put "K... " scripts in /etc/rcS.d (1x)

        3 reboot -- -s (2x)

        4 init 0 or /etc/shutdown, then "boot -s" (4x)

        5 touch /etc/nologin (1x)

        On the other hand, or so I have been told, if you "touch
        /etc/nologin" while in multiuser mode then logins are not
        allowed. NOTE: This file '/etc/nologin' is automatically
        checked for and removed upon reboot.

        6 halt the machine, then "boot -s" (2x)

3 Solution Adopted

        I used boot -s from the prom monitor's ok prompt. Thanks! But
some of these other methods look intrigueing and I'll investigate them
later. I'm a bit wary of "halt then boot -s". If you Stop A (halt?) then
wouldn't you need to do a sync first before the boot? Anyway, I'm
relieved that it is not necesary to put K scripts in /etc/rcS.d, which is
what I had been fearing that I would have to do.

4 Original Posting

I want to enter single user mode to install patches on my Sun Sparc Classic
Solaris 2.4 machine, but when I do init 1 or init S or init s there are
still many many processes running including in.routed, automountd and
sendmail -bd. Users can still log in over the network. What should I do?

This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:18 CDT