01-27-2010
The RH300 training material covers it in detail.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi Expert,
I have encountered some problem with my SUN system. Everytime when i issue command #init 6 OR #init 0 it just logout and prompt for login again instead of rebooting the server when run init 6 and system shutdown when run init 0..
I can only reboot the system using reboot ... Was... (6 Replies)
Discussion started by: sc2005
6 Replies
2. Solaris
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. Solaris
Hi,
Am new to solaris.Can anyone explains me the difference between using init and shutdown command. As per my knowledge shutdown will give notification to users, is there anything apart from that.
thanks in advance. (6 Replies)
Discussion started by: rogerben
6 Replies
4. Linux
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
5. Solaris
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies
6. Red Hat
What's the difference between the two. I've seen xinit.d directory not always but on some systems. (1 Reply)
Discussion started by: Praveen_218
1 Replies
7. UNIX for Advanced & Expert Users
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
8. Solaris
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
9. Red Hat
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
10. Red Hat
Hi,
Guys can any one explain me the difference between init s and init 1 in linux?
this would be very useful....
thanx in advance..
regards
Amandeep (3 Replies)
Discussion started by: aman.singh2886
3 Replies
LEARN ABOUT MOJAVE
service
SERVICE(8) System Manager's Manual SERVICE(8)
NAME
service - run a System V init script
SYNOPSIS
service SCRIPT COMMAND [OPTIONS]
service --status-all
service --help | -h | --version
DESCRIPTION
service runs a System V init script or systemd unit in as predictable an environment as possible, removing most environment variables and
with the current working directory set to /.
The SCRIPT parameter specifies a System V init script, located in /etc/init.d/SCRIPT, or the name of a systemd unit. The existence of a
systemd unit of the same name as a script in /etc/init.d will cause the unit to take precedence over the init.d script. The supported val-
ues of COMMAND depend on the invoked script. service passes COMMAND and OPTIONS to the init script unmodified. For systemd units, start,
stop, status, and reload are passed through to their systemctl/initctl equivalents.
All scripts should support at least the start and stop commands. As a special case, if COMMAND is --full-restart, the script is run twice,
first with the stop command, then with the start command.
service --status-all runs all init scripts, in alphabetical order, with the status command. The status is [ + ] for running services, [ - ]
for stopped services and [ ? ] for services without a status command. This option only calls status for sysvinit jobs.
EXIT CODES
service calls the init script and returns the status returned by it.
FILES
/etc/init.d
The directory containing System V init scripts.
/{lib,run,etc}/systemd/system
The directories containing systemd units.
ENVIRONMENT
LANG, LANGUAGE, LC_CTYPE, LC_NUMERIC, LC_TIME, LC_COLLATE, LC_MONETARY, LC_MESSAGES, LC_PAPER, LC_NAME, LC_ADDRESS, LC_TELEPHONE, LC_MEA-
SUREMENT, LC_IDENTIFICATION, LC_ALL, TERM, PATH
The only environment variables passed to the init scripts.
SEE ALSO
/etc/init.d/skeleton
update-rc.d(8)
init(8)
invoke-rc.d(8)
systemctl(1)
AUTHOR
Miloslav Trmac <mitr@redhat.com>, Petter Reinholdtsen <pere@hungry.com>
Licence: GNU Public Licence v2 (GPLv2)
COPYRIGHT
2006 Red Hat, Inc., Petter Reinholdtsen <pere@hungry.com>
Jan 206 SERVICE(8)