topic Re: init s versus init S in Operating System - HP-UX

init s versus init S

j773303 — Fri, 03 Jan 2003 03:12:21 GMT

As title, what's the different on both?
Thanks.

Re: init s versus init S

Scott Van Kalken — Fri, 03 Jan 2003 03:15:21 GMT

S|s Use for system administration (also known as "single-
user state"). When booting into run level S at powerup,
the only access to the the system is through a shell
spawned at the system console as the root user. The
only processes running on the system will be kernel
daemons started directly by the HP-UX kernel, daemon
processes started from entries of type sysinit in
/etc/inittab, the shell on the system console, and any
processes started by the system administrator.
Administration operations that require the system to be
in a quiescent state (such as the fsck(1M) operation to
repair a file system) should be run in this state.
Transitioning into run level S from a higher run level
does not terminate other system activity and does not
result in a "single-user state"; this operation should
not be done.

This is from the init man page.

Re: init s versus init S

j773303 — Fri, 03 Jan 2003 03:24:59 GMT

In run level S(uppercase S) the capabilities of the system console are switched to the terminal where you are logged in, thus making
it the virtual system console.

I don't understand what the above meaning. What's the meaning of virtual system console?

Re: init s versus init S

Patrick Wallek — Fri, 03 Jan 2003 03:37:40 GMT

What it means is that if you do an 'init S', thus going down to single-user mode, AND IF you were logged into a serially connected terminal (or maybe modem) that the terminal you are logged into would BECOME the console.

I do not know, though I doubt, that this applies to a telnet session. Networking gets stopped between runlevels 2 and 1, I think, so your telnet would be disconnected.

BASICALLY, in this world of few hardwired terminals and many network connections, the two are the same.

Re: init s versus init S

Rajeev Shukla — Fri, 03 Jan 2003 03:48:58 GMT

THis basically means that the terminal from where you issue this command init S becomes your console. And its only for serial devices not for telnet sessions. So if you issue the init S after doing telnet to the system the console doesn't swicth to that device but when you are on a serial (dumb terminal) link, when you are in single user this terminal is your console.

Cheers
Rajeev

Re: init s versus init S

Bill Hassell — Fri, 03 Jan 2003 05:50:42 GMT

VERY IMPORTANT: init s or init S will only adjust the init program's view of things. That is, init does not own all processes in HP-UX so using init S/s to enter single user mode (despite the init man page) will not be successful. init will not un-mount filesystems or terminate daemons, etc. Essentially, init S/s will look at the processes that it owns and if they are not listed in /etc/inittab when changing to S/s state, then those proceses are terminated. All other processes continue running.

Re: init s versus init S

Daryl Much — Thu, 17 Jun 2004 09:54:01 GMT

Bill response is the crux of the biscuit. Init s|S is usually worthless in my experience. If you really want to be single user, reboot to IPL then enter hpux -is.