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..
10 More Discussions You Might Find Interesting
1. Solaris
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
Hi,
What is the difference between those two ?
thanks
Vilius (1 Reply)
Discussion started by: vilius
1 Replies
3. 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
4. Red Hat
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
what are the major Difference Between run level & init level (2 Replies)
Discussion started by: rajaramrnb
2 Replies
6. UNIX for Dummies Questions & Answers
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
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
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
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
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
LEARN ABOUT REDHAT
pam_console
pam_console(8) System Administrator's Manual pam_console(8)
NAME
pam_console - control permissions for users at the system console
SYNOPSIS
session optional /lib/security/pam_console.so
auth required /lib/security/pam_console.so
DESCRIPTION
pam_console.so is designed to give users at the physical console (virtual terminals and local xdm-managed X sessions by default, but that
is configurable) capabilities that they would not otherwise have, and to take those capabilities away when the are no longer logged in at
the console. It provides two main kinds of capabilities: file permissions and authentication.
When a user logs in at the console and no other user is currently logged in at the console, pam_console.so will change permissions and own-
ership of files as described in the file /etc/security/console.perms. That user may then log in on other terminals that are considered
part of the console, and as long as the user is still logged in at any one of those terminals, that user will own those devices. When the
user logs out of the last terminal, the console may be taken by the next user to log in. Other users who have logged in at the console
during the time that the first user was logged in will not be given ownership of the devices unless they log in on one of the terminals;
having done so on any one terminal, the next user will own those devices until he or she has logged out of every terminal that is part of
the physical console. Then the race can start for the next user. In practice, this is not a problem; the physical console is not gener-
ally in use by many people at the same time, and pam_console.so just tries to do the right thing in weird cases.
ARGUMENTS
debug turns on debugging
allow_nonroot_tty
gain console locks and change permissions even if the TTY's owner is not root.
permsfile=filename
tells pam_console.so to get its permissions database from a different file than /etc/security/console.perms
fstab=filename
tells pam_console.so to read the table of configured filesystems from a file other than /etc/fstab when scanning permsfile. This
file is used to map directories to device names.
FILES
/var/run/console.lock
/var/run/console/
/etc/security/console.apps
/etc/security/console.perms
SEE ALSO
console.perms(5)
console.apps(5)
/usr/doc/pam*/html/index.html pam_console_apply(8)
/usr/doc/pam*/html/index.html
BUGS
Let's hope not, but if you find any, please report them via the "Bug Track" link at http://bugzilla.redhat.com/bugzilla/
AUTHOR
Michael K. Johnson <johnsonm@redhat.com>
Red Hat 2000/7/11 pam_console(8)