05-15-2006
im running slackware 3.3, its my personal laptop, no server-side anything.
im logged in as root most of the time, im not in a situation where im physically interacting with the laptop at the moment, so i cannot respond to the uname -a part, but i will in a little later..
and shutdown -h now.... just means to halt now... ive tried that, as well as shutdown -n -h now in hopes to give a quick kill, but to no avail..
9 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi Friends,
We have migrated our Unix from HP True 64 v5.1 to HP-UX B.11.11i recently and copied all my shell scripts ( Korn shell ) to new HP-UX B.11.11i unix machine. I've encountered lot of errors during execution of the scripts for example:
cat x.sh
#!/usr/bin/ksh
if
then
echo... (3 Replies)
Discussion started by: krishna
3 Replies
2. UNIX for Dummies Questions & Answers
hi
i think this will make me seem dummier than most, actually i don't even understand most of the posts in the dummie section...
i have a project and i need to learn fortran programming, im working on a windows xp pc and so i have installed cygwin. and the cygwin site basically says learn unix so... (4 Replies)
Discussion started by: holyhive
4 Replies
3. UNIX for Dummies Questions & Answers
I have heard for a long time that in maybe 2039 Unix will no longer be useable due the length of the date value. Anyone know anything about this? (4 Replies)
Discussion started by: dhlopomo
4 Replies
4. Shell Programming and Scripting
Hi guys,
I'm new to unix but loving it!! BUT this is driving me nuts as i can't work out the best way to do it.
I have a while true loop that i use to monitor something. For my own reasons in ths script i have disabled the CTRL C using the trap command. But i want to put in a option to exit... (5 Replies)
Discussion started by: Noob e
5 Replies
5. UNIX for Dummies Questions & Answers
Hallo everybody
I am having a shell script called auto_run.sh in that only the first line works.
the second line which has sed command is working only at the # prompt. not within the shell script. What could be the reason.
*... sed 's/ //g' KTI >abc works in another shell script without the... (6 Replies)
Discussion started by: naushad
6 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. Shell Programming and Scripting
Hi
I need help with a script to loop unitl the statement is true
done some thing like this
until
if
then
cp filename filename.anto
fi
done
Regards, (3 Replies)
Discussion started by: antointoronto
3 Replies
8. Shell Programming and Scripting
hi,
i am new in bash scripting.
i am trying to write a Bash script to monitor how many process are running in my Redhat6 Linux machine.
example :
let say there must be always 5 process from the same kind that must run and if one off them fails down the script must wake up another process... (2 Replies)
Discussion started by: zigizag
2 Replies
9. Shell Programming and Scripting
Hi Team,
I need to know why ppl use If true loop instead of just writing down the sequence of code lines.
1:
echo "Line1"
if true; then
echo "Line2"
fi
echo "Line3"
2:
echo "Line1"
echo "Line2"
echo "Line3"
Could you explain what does the if true loop make difference in 1st compare... (3 Replies)
Discussion started by: chandana hs
3 Replies
LEARN ABOUT MOJAVE
shutdown
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