02-16-2008
First s == S; init accepts either upper or lower case s. The meaning of s is built into the init program itself. If init comes up in level s, /etc/inittab is ignored. If init had been in a numeric run level, init will transition down to a point where /etc/inittab is ignored. This is the original and official single user mode. It is the only mode that works if /etc/inittab is missing. While init is in level S, init will ignore requests to reread /etc/inittab. In level S, init would originally connect a shell to the system console so that commands can be entered. Some versions of init, including Sun's, have a change to connect the login program to the console. This change makes the system more secure, but now booting up to single user requires /etc/passwd and /etc/shadow. Some versions of init can do either behavior depending on the security level of the OS. But all of this is built in to init and cannot be changed by modifying /etc/inittab.
The numeric run levels are under the control of the author of /etc/inittab. Sun uses:
0 = firmware mode...OS will die and you get the "ok" prompt
1 = "administrative" mode, Sun's replacement for single user mode with a very few things running
2 = multi-user mode, a lot of stuff running and people can sign on
3 = makes local resources available to other systems
4 = not used
5 = power down the system
6 = reboot the system
So "init 0" is very different... no OS at all will be running. Level s and Level S are different names for the same thing. Level S and 1 are very close in concept. The difference is that a few things will be running in level 1 and level 1 requires a good /etc/inittab.
Also Sun and everyone else cheat a little bit. If you are in a high level and enter level S, you do not really go all the way down to a "true" level S. They will leave a few things running. This leads the system admin's rule that a "true" level S is achieved only by rebooting and coming up directly to level S. This is partially because of intent and partially because some stuff just will not die.
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
When the solaris 8 have come up, which command can find out the current run-level?
thanks. (2 Replies)
Discussion started by: nianzhe
2 Replies
2. SuSE
Hello,
I recently updated a test system from Suse 8 to 9.3. Now our runlevel services program doesn't work, but works fine on our other 9.3 boxes.
We have a file in /etc/init.d/rc3.d called S99fooprog(not actual name ofcourse).
It just has a command to start a program daemon up. Anyways... (3 Replies)
Discussion started by: benefactr
3 Replies
3. Solaris
Hi Experts,
A stupid question for experts :confused: !!
What is the difference between run level ‘1', runlevel ‘S' and small ‘s'.
As per my understanding the difference between S and 1 is that in case of ‘S' it only going to mount the critical file system which ideal should be... (2 Replies)
Discussion started by: kumarmani
2 Replies
4. UNIX for Advanced & Expert Users
Hi,
Could somebody throw some light on the below queries:
- For a run-level X, the S* scripts are executed when coming here from X-n run-level. The K* scripts are executed when coming to X runlevel from X+n runlevel.
- Does reaching to runlevel X from X-3 executes K* scritps from X-2 & X-1... (4 Replies)
Discussion started by: vibhor_agarwali
4 Replies
5. Solaris
Hi All,
In Solaris 9 and below
I will get the init run-level by checking the /etc/inittab entry
is:3:initdefault:
But in Solaris 10 we are using the smf functionality.
Here how I can get the init default run level.
Please help me in this problem.
Regards,
... (2 Replies)
Discussion started by: kalpeer
2 Replies
6. Solaris
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies
7. UNIX for Dummies Questions & Answers
A Bourne Shell script is placed in /etc/rc.d/rc3.d called S57apache. What will happen with this script when the run level is changed from 5 to 3?
many thanks (4 Replies)
Discussion started by: lemon_06
4 Replies
8. Solaris
Hello,
I'm creating a VM Image of Solaris 10 on VM Player. I've completed the installation & I am using the Java Desktop as my default logon. I need to modify the Run Level to Console Mode (permanently). Unlike previous versions or Linux, modifying inittab file is not an option here.
Please... (2 Replies)
Discussion started by: DevendraG
2 Replies
9. Shell Programming and Scripting
Is there a way to tell what runlevel is currently being used,
for example is a user is using the gui
or is the have pressed Alt+Ctrl+F1 to drop to the terminal?? (3 Replies)
Discussion started by: ab52
3 Replies
10. Solaris
for solaris 11, how does one change the run level at boot from 3 to 2?
i checked "/etc/inittab" file where i usually change it in other *nix but it seems solaris is not using it. (1 Reply)
Discussion started by: badbanana
1 Replies
LEARN ABOUT DEBIAN
fl-run-test
FL-RUN-TEST(1) Debian manual FL-RUN-TEST(1)
NAME
fl-run-test - runs a funkload test file
SYNOPSIS
fl-run-test [ options ] file [ class.method | class | suite ]
DESCRIPTION
A FunkLoad test can be used like a standard unittest using a unittest.main() and a 'python MyFile.py'.
Note that fl-run-test can be used to launch normal unittest.TestCase and (if you use python2.4) doctest in a plain text file or embedded in
a python docstring. The --debug option makes doctests verbose.
OPTIONS
--version
show program's version number and exit
--help, -h
show this help message and exit
--quiet, -q
Minimal output.
--verbose, -v
Verbose output.
--debug, -d
FunkLoad and doctest debug output.
--debug-level=DEBUG_LEVEL
Debug level 3 is more verbose.
--url=MAIN_URL, -uMAIN_URL
Base URL to bench without ending '/'.
--sleep-time-min=FTEST_SLEEP_TIME_MIN, -mFTEST_SLEEP_TIME_MIN
Minumum sleep time between request.
--sleep-time-max=FTEST_SLEEP_TIME_MAX, -MFTEST_SLEEP_TIME_MAX
Maximum sleep time between request.
--dump-directory=DUMP_DIR
Directory to dump html pages.
--firefox-view, -V
Real time view using firefox, you must have a running instance of firefox in the same host.
--no-color
Monochrome output.
--loop-on-pages=LOOP_STEPS, -lLOOP_STEPS
Loop as fast as possible without concurrency on pages expect a page number or a slice like 3:5. Output some statistics.
--loop-number=LOOP_NUMBER, -nLOOP_NUMBER
Number of loop.
--accept-invalid-links
Do not fail if css/image links are not reachable.
--simple-fetch
Don't load additional links like css or images when fetching an html page.
--stop-on-fail
Stop tests on first failure or error.
--regex=REGEX, -eREGEX
The test names must match the regex.
--list Just list the test names.
--pause
Pause between request, press ENTER to continue.
SEE ALSO
fl-build-report(1), fl-credential-ctl(1), fl-install-demo(1), fl-monitor-ctl(1), fl-record(1), fl-run-bench(1).
AUTHOR
Funkload was written by Benoit Delbosc.
This manual page was written by Jose Parrella <bureado@debian.org>, for the Debian project (but may be used by others).
Debian Project 26 March 2009 FL-RUN-TEST(1)