Sponsored Content
Full Discussion: Init 6 & Init 0 problem
Top Forums UNIX for Advanced & Expert Users Init 6 & Init 0 problem Post 82533 by Unbeliever on Friday 2nd of September 2005 05:30:59 AM
Old 09-02-2005
Quote:
Originally Posted by bakunin
First off, the command to switch runlevels is not "init", but "telinit".
FYI this is not strictly true on Suns. The telinit command (/etc/telinit) is simply a soft link to /sbin/init. So strickly speaking init it the command and telinit is the alias.

Does ths shutdown command do the same thing for you? You can change system runtime levels with it in much the same way as init except there is a slight delay even if you specify 0 delay :-)

For init level 0, no wait time, dont ask for confirmation:

shutdown -g0 -i0 -y

For init level 6, no wait time, dont ask for confirmation:

shutdown -g0 -i6 -y
 

10 More Discussions You Might Find Interesting

1. Linux

Problem of booting system in init 5 level

Hi, I am using RHEL4 and I am not booting my computer into graphics mode i.e. It gets hangs after the step of Enabling swap space... I.e system is not able to enter into runlevel 5. However, when I boot it into 'runlevel3' and then I do "#startx", It enetrs... (1 Reply)
Discussion started by: jagdish.machhi@
1 Replies

2. Solaris

different between /sbin/init and /usr/sbin/init

root@test09 # ls -al /sbin/init -r-xr-xr-x 1 root sys 550000 Jun 29 2002 /sbin/init root@test09 # ls -al /usr/sbin/init -r-xr-xr-x 1 root sys 37100 Jun 29 2002 /usr/sbin/init (2 Replies)
Discussion started by: userking
2 Replies

3. UNIX for Dummies Questions & Answers

About init

I know if a parent process exits before its child, the last one becomes orphan for a while and then is added to the children of Init process. I'd like to know deeper 1 how the orphan becomes init process, 2 how init knows that from a some point on it has another child. Thank you in advance. (2 Replies)
Discussion started by: Puntino
2 Replies

4. Shell Programming and Scripting

Problem regarding Sed/Echo/Var Init

Greetings, I've visited this forums for a long time and normally got an right answer but this time my problem doesn't seem to go away. What I'm trying to do is the following: VAR="\n\nline1\nline2\nline3\nline4\nline5\nline6\nline7\n\n" (The count of newlines is varying!) If I echo this i... (3 Replies)
Discussion started by: ph1l
3 Replies

5. Linux

How to I change init levels after typing init 1

Dear all, I typed in init 1 on my redhat box as root and according to wikipedia (http://en.wikipedia.org/wiki/Runlevel): 1 Single-User Mode Does not configure network interfaces, start daemons, or allow non-root logins So now I can't connect back to it. How do I change the init back to 3?... (8 Replies)
Discussion started by: z1dane
8 Replies

6. Red Hat

Difference between 'init s' and 'init 1'

What is the difference between 'init s' and 'init 1'. I know that both will work to change the current run level to single user mode. Is there any difference in those two commands? (5 Replies)
Discussion started by: praveen_b744
5 Replies

7. Solaris

Difference between run level & init level

what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies

8. UNIX for Advanced & Expert Users

Problem on init 0, execution is the same with init 6

Hi, I am experiencing a weird thing on my SUNFIRE machine with Solaris 9 OS. When I do init 0 to shutdown the machine to go to ok prompt, what it did was shutdown and reboot like an init 6 command do. I did check the corresponding rc scripts that were involved with init 0 and compared with rc... (2 Replies)
Discussion started by: Yenthanh
2 Replies

9. Solaris

What is the diffe b/w init s and init S

i did my research in finding the answer but couldn't find right one. Please give your inputs. (6 Replies)
Discussion started by: ranumala
6 Replies

10. Red Hat

init-script failing because of /etc/rc.d/init.d/functions

I encountered a problem on one of our database servers. OS: CentOS 5.5 final Kernel: 2.6.18-238.5.1.el5.028stab085.2 (OpenVZ kernel) We wrote some DB-Start/Stop-scripts ("/db2/admin/scripts_dba/start_services.ksh" and ".../stop_services.ksh") to start the database instances. (Database... (1 Reply)
Discussion started by: bakunin
1 Replies
init(8) 						      System Manager's Manual							   init(8)

NAME
init - Upstart process management daemon SYNOPSIS
init [OPTION]... DESCRIPTION
init is the parent of all processes on the system, it is executed by the kernel and is responsible for starting all other processes; it is the parent of all processes whose natural parents have died and it is responsible for reaping those when they die. Processes managed by init are known as jobs and are defined by files in the /etc/init directory. See init(5) for more details on configur- ing Upstart. Events init(8) is an event-based init daemon. This means that jobs will be automatically started and stopped by changes that occur to the system state, including as a result of jobs starting and stopping. This is different to dependency-based init daemons which start a specified set of goal jobs, and resolve the order in which they should be started and other jobs required by iterating their dependencies. For more information on starting and stopping jobs, as well as emitting events that will automatically start and stop jobs, see the manual page for the initctl(8) tool. The primary event is the startup(7) event, emitted when the daemon has finished loading its configuration. Other useful events are the starting(7), started(7), stopping(7) and stopped(7) events emitted as jobs change state. See upstart-events(7) for a summary of well-known events. System V compatibility The Upstart init(8) daemon does not keep track of runlevels itself, instead they are implemented entirely by its userspace tools. The event emitted to signify a change of runlevel is the runlevel(7) event. For more information see its manual page. OPTIONS
Options are passed to init(8) by placing them on the kernel command-line. --confdir directory Read job configuration files from a directory other than /etc/init. --no-sessions Disable user and chroot sessions. --no-startup-event Suppress emission of the initial startup event. This option should only be used for testing since it will stop the init(8) daemon from starting any jobs automatically. --session Connect to the D-Bus session bus. This should only be used for testing. --startup-event event Specify a different initial startup event from the standard startup(7). --verbose Outputs verbose messages about job state changes and event emissions to the system console or log, useful for debugging boot. NOTES
init is not normally executed by a user process, and expects to have a process id of 1. If this is not the case, it will actually execute telinit(8) and pass all arguments to that. See that manual page for further details. FILES
/etc/init.conf /etc/init/*.conf $HOME/.init/ AUTHOR
Written by Scott James Remnant <scott@netsplit.com> REPORTING BUGS
Report bugs at <https://launchpad.net/upstart/+bugs> COPYRIGHT
Copyright (C) 2009-2011 Canonical Ltd. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. SEE ALSO
control-alt-delete(7) init(5) initctl(8) runlevel(7) startup(7) starting(7) started(7) stopping(7) stopped(7) telinit(8) upstart-events(7) Upstart 2011-04-06 init(8)
All times are GMT -4. The time now is 05:52 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy