Sponsored Content
Operating Systems Solaris difference between init and shutdown Post 302335942 by rogerben on Monday 20th of July 2009 08:09:43 PM
Old 07-20-2009
Quote:
Originally Posted by ilikecows
Shutdown also sends a message to the console informing all users that the system is about to go down. Any user with a terminal attached to the console will receive this message in that terminal.
Pls can you explain ur point more clearly..
rogerben
 

10 More Discussions You Might Find Interesting

1. Solaris

difference b/w halt shutdown

Hi, I want to know the difference between halt and shutdown commands and which is better to use? Regards, visu (2 Replies)
Discussion started by: visu_ak
2 Replies

2. AIX

Difference between "shutdown" and "shutdown -h" ?

Hi, What is the difference between those two ? thanks Vilius (1 Reply)
Discussion started by: vilius
1 Replies

3. 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

4. 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

5. 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

6. UNIX for Dummies Questions & Answers

Script to force Oracle database shutdown when shutdown immediate does not work

I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS). Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies

7. Red Hat

The difference between init.d and xinit.d dir ...

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

8. 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

9. Red Hat

Difference b/w init s and init1 in red hat linux?

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

10. UNIX for Beginners Questions & Answers

No init messages display during startup/shutdown

This question is more in the line of how init messages get sent to a console during startup/shutdown. My problem has to do with exporting a VM from AWS to KVM (and a retry on virtual box). I am looking for a understanding on how init messages are sent to a device and what controls them My two... (0 Replies)
Discussion started by: jtkells
0 Replies
VLOCK(1)						      General Commands Manual							  VLOCK(1)

NAME
vlock - Virtual Console lock program SYNOPSIS
vlock vlock [ -a,--all ] [ -c,--current ] [ -h,--help ] [ -v,--version ] DESCRIPTION
vlock is a program to lock one or more sessions on the Linux console. This is especially useful for Linux machines which have multiple users with access to the console. One user may lock his or her session(s) while still allowing other users to use the system on other vir- tual consoles. If desired, the entire console may be locked and virtual console switching disabled. By default, only the current VC (virtual console) is locked. With the -a,-all option all VCs are locked. The locked VCs cannot be unlocked without the invoker's password. And, for the paranoid, vlock makes it a trying experience for those attempting to guess the pass- word, so unauthorized access to session(s) is highly unlikely. Please note that it is entirely possible to completely lock yourself out of the console with the -a,--all option if you cannot remember your password! Unless you are able to kill vlock by logging in remotely via a serial terminal or network, a hard reset is the only method of ``unlocking'' the display. vlock works for console sessions primarily. However, there is support for trying to lock non-console sessions as well, but that support has not been well tested. OPTIONS
-a,--all Lock all console sessions and disable VC switching. -c,--current Lock the current session (this is the default). -h,--help Print a brief help message. -v,--version Print the version number of vlock. AUTHOR
Michael K. Johnson <johnsonm@redhat.com> Linux User's Manual 16 May 1996 VLOCK(1)
All times are GMT -4. The time now is 10:10 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy