09-21-2011
These aren't typical users, but rather a processes that the system uses internally, for example, to shutdown the system - it will simply invoke the process of shutting down.
Also, generally users usually takes numbers above 500 in this file, and numbers below 100 are reserved for system use, as in this case. As you can see, they have no shell assigned.
There's also a legacy reason - on some older Linux distros you could use SU to these users and shutdown the system.
10 More Discussions You Might Find Interesting
1. Post Here to Contact Site Administrators and Moderators
Need to eventually sync the MY.UNIX userdata to the forums database (and others). Suggestions on the best approach welcome. (0 Replies)
Discussion started by: Neo
0 Replies
2. UNIX for Advanced & Expert Users
What's the idea of Unsyncron SUN WS's ? one of our client had a problem & my supervisor told me that this causes of unsynchron WS's i mean maybe the setting of one is not compatible with other .....
Any Suggestion would be helpful
Rgrds,
nikk (1 Reply)
Discussion started by: nikk
1 Replies
3. UNIX for Advanced & Expert Users
I am neither advanced nor expert. I have synced two linux machines, from Debian to Fedora. I brought whole "home" directory. Which directory or files should bring to Fedora in order to have same user login and password? (2 Replies)
Discussion started by: kumarrana
2 Replies
4. Solaris
Hi all....I have a Sun Ultra2 that I want to use with my PC monitor. I have purchased an adapter that does not work and I was told I need to change my video card setting (if I can) to Separate Sync.....my Monitor product number ends in 1343......I am running SunOS 5.7 ......anyone have any ideas?
... (0 Replies)
Discussion started by: psantinello
0 Replies
5. 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
6. UNIX for Dummies Questions & Answers
Folks;
I have 2 SUSE DNS servers, one will be the master and one will be the slave. we normally update the master when adding any new servers to the DNS list.
I'm looking for a way to sync both servers every night, so the slave is updated nightly.
I thought of using "rsync" with cron to sync... (1 Reply)
Discussion started by: Katkota
1 Replies
7. Red Hat
Hi All,
I want to know is there any way where if i add a user in a centos machine the can be replicated to another centos automatically.
As i have setup DRBD with heartbeat for apache webserver everything is working fine but the only thing im stuck in is about system account for ftp.
Can any... (3 Replies)
Discussion started by: search4u2003
3 Replies
8. Red Hat
User shutdown detected - cssd(16694)CRS-1603:CSSD. Can you help me with this error in redhat linux server (1 Reply)
Discussion started by: karthik9358
1 Replies
9. Red Hat
hi guys!
I like to know which user has rebooted or shutdown a redhat box ?
the thing is wanted to know the exact user name who has done this action, ofcourse an admin privileged user only can do this. from a list of admin privileged user to find the exact one.
i used to go with last... (4 Replies)
Discussion started by: redhatlbug
4 Replies
10. UNIX for Dummies Questions & Answers
Hi Guru's
Am looking for linux reboot command which get executed after user confirmation .Can someone please help me with this.:confused::confused::confused: (6 Replies)
Discussion started by: kapil514
6 Replies
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown -- close down the system at a given time
SYNOPSIS
shutdown [-] [-h [-u] | -r | -s | -k] [-o [-n]] time [warning-message ...]
DESCRIPTION
The shutdown utility provides an automated shutdown procedure for super-users to nicely notify users when the system is shutting down, saving
them from system administrators, hackers, and gurus, who would otherwise not bother with such niceties.
The following options are available:
-h The system is halted at the specified time.
-k Kick everybody off. The -k option does not actually halt the system, but leaves the system multi-user with logins disabled (for all
but super-user).
-n If the -o is specified, prevent the file system cache from being flushed by passing -n option to halt(8) or reboot(8). This option
should probably not be used.
-o If -h or -r is specified, shutdown will execute halt(8) or reboot(8) instead of sending a signal to launchd(8).
-r The system is rebooted at the specified time.
-s The system is put to sleep at the specified time.
-u The system is halted up until the point of removing system power, but waits before removing power for 5 minutes so that an external
UPS (uninterruptible power supply) can forcibly remove power. This simulates a dirty shutdown to permit a later automatic power on.
OS X uses this mode automatically with supported UPSs in emergency shutdowns.
time Time is the time at which shutdown will bring the system down and may be the word now (indicating an immediate shutdown) or specify a
future time in one of two formats: +number, or yymmddhhmm, where the year, month, and day may be defaulted to the current system val-
ues. The first form brings the system down in number minutes and the second at the absolute time specified.
warning-message
Any other arguments comprise the warning message that is broadcast to users currently logged into the system.
- If '-' is supplied as an option, the warning message is read from the standard input.
At intervals, becoming more frequent as apocalypse approaches and starting at ten hours before shutdown, warning messages are displayed on
the terminals of all users logged in.
At shutdown time a message is written to the system log, containing the time of shutdown, the person who initiated the shutdown and the rea-
son. Corresponding signal is then sent to launchd(8) to respectively halt, reboot or bring the system down to single-user state (depending
on the above options).
A scheduled shutdown can be canceled by killing the shutdown process (a SIGTERM should suffice).
SIGTERM TO SIGKILL INTERVAL
Upon shutdown, all running processes are sent a SIGTERM followed by a SIGKILL. The SIGKILL will follow the SIGTERM by an intentionally inde-
terminate period of time. Programs are expected to take only enough time to flush all dirty data and exit. Developers are encouraged to
file a bug with the OS vendor, should they encounter an issue with this functionality.
SEE ALSO
kill(1), login(1), wall(1), halt(8), launchd(8), reboot(8)
BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
HISTORY
The shutdown utility appeared in 4.0BSD.
BSD
December 11, 1998 BSD