10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I'm writing a script to stop & start oracle:
su - oracle -c "sqlplus / as sysdba" -c "shutdown immediate">> ${log} 2>&1
The {log} refers to the log file. The part in bold gives error:
/usr/sbin/shutdown: Only root can run /usr/sbin/shutdown
Pls suggest how to correct this.
... (5 Replies)
Discussion started by: frum
5 Replies
2. AIX
Hi All,
I would like to schedule auto IPL (shutdown and start-up) by using a shell script.
Can you please give me some idea?
want to test on my lab box first.
shell script should bring AIX LPAR down and then need to start/activate the LPAR after 30 min
any idea is highly... (3 Replies)
Discussion started by: System Admin 77
3 Replies
3. Shell Programming and Scripting
Dear Experts ,
I want to stop and Start tomcat at the time of shutdown and startup of our server . I was trying to stop tomcat with following command
# su - dm -c "/export/home/Finder/FinderWeb/jakarta-tomcat-3.3.1a/bin/shutdown.sh"
but i am getting following error. Please suggest .... (1 Reply)
Discussion started by: Amit.saini333
1 Replies
4. AIX
hi,
If we place Sxx (startup script) and Kxx(shutdown script) in /etc/rc.d/rc2.d,then it would start and stop automatically(assume they are linked to other script that actually starts/stops).
is there really a link needed here to /etc/rc.d/init.d? if not,what is the use of this directory..?... (1 Reply)
Discussion started by: to_bsr
1 Replies
5. Solaris
Are rc scripts executed serially or all at the same time. Is there a way to see this happen? A log file or the syslogd?
This is Solaris 10. (2 Replies)
Discussion started by: djehresmann
2 Replies
6. UNIX for Dummies Questions & Answers
Having difficulty trying to locate startup and shutdown messages. I had a bunch of servers shutdown over the weekend (due to a scheduled power outage) and upon reboot a lot of the filesystems weren't mounted and several processes weren't started...
I checked /var/adm/messages and can't locate... (2 Replies)
Discussion started by: jamie_collins
2 Replies
7. 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
8. SuSE
The wtmp file records all logins and logouts. Its format is exactly like utmp except that a null user name indicates a logout on the associated terminal. Furthermore, the terminal name "~" with user name "shutdown" or "reboot" indicates a system shutdown or reboot and the pair of terminal names... (1 Reply)
Discussion started by: Laksmi
1 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I modified my inittab file in the /etc directory. When I started up my machine, system hangs on initialization. I'm trying to remove what I added in the inittab file so that everything is back to normal.
I'm using AIX 5 and I would like to boot up so I can get back into a regular... (0 Replies)
Discussion started by: dhuser
0 Replies
10. AIX
I understand that by putting in entries into the /etc/inittab file. We can actually call the our scripts during startup.
mkitab "start_server:2:once:sh /scripts/startserver.sh"
Would the system wait for startserver.sh finish executing before it goes to another entry? and how long would it... (1 Reply)
Discussion started by: vincente
1 Replies
SHUTDOWN(8) BSD System Manager's Manual SHUTDOWN(8)
NAME
shutdown -- close down the system at a given time
SYNOPSIS
shutdown [-Ddfhknprvxz] [-b bootstr] time [message ... | -]
DESCRIPTION
shutdown 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.
Available friendlinesses:
-b bootstr
The given bootstr is passed to reboot(8) for the benefit of those systems that can pass boot arguments to the firmware. Currently,
this only affects sun3 and sparc machines.
-d shutdown will pass the -d flag to reboot(8) or halt(8) to request a kernel core dump. If neither the -h or -r flags are specified,
then -d also implies -r.
-f shutdown arranges, in the manner of fastboot(8), for the file systems not to be checked on reboot.
-h The system is halted at the specified time, using halt(8).
-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 Prevent the normal sync(2) before stopping.
-p The system is powered down at the specified time, using poweroff(8). If the powerdown fails, or the system does not support soft-
ware powerdown, the system will simply halt instead.
-r The system is rebooted at the specified time, using reboot(8).
-v To enable verbose messages on the console, pass -v to reboot(8) or halt(8).
-x To enable debugging messages on the console, pass -x to reboot(8) or halt(8).
-z To silence some shutdown messages on the console, pass -z to reboot(8) or halt(8).
-D Prevents shutdown from detaching from the tty with fork(2)/ exit(3).
time Time is the time at which shutdown will bring the system down and may be the word now or a future time in one of two formats:
+number, or [[[[[cc]yy]mm]dd]hh]mm, where the century, year, month, day, and hour may be defaulted to the current system values.
The first form brings the system down number minutes from the current time; the second brings the system down at the absolute time
specified. If the century is not specified, it defaults to 1900 for years between 69 and 99, or 2000 for years between 0 and 68. A
leading zero in the ``yy'' value is not optional.
message ...
Any other arguments comprise the warning message that is broadcast to users currently logged into the system.
- If - is supplied as the only argument after the time, the warning message is read from the standard input.
BEHAVIOR
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. Five minutes before shutdown, or immediately if shutdown is in less than 5 minutes, logins are dis-
abled by creating /etc/nologin and copying the warning message there. If this file exists when a user attempts to log in, login(1) prints
its contents and exits. The file is removed just before shutdown exits.
At shutdown time, a message is written in the system log containing the time of shutdown, who initiated the shutdown, and the reason. Next a
message is printed announcing the start of the system shutdown hooks. Then the shutdown hooks in /etc/rc.shutdown are run, and a message is
printed indicating that they have completed. After a short delay, shutdown runs halt(8) or reboot(8), or sends a terminate signal to init(8)
to bring the system down to single-user mode, depending on the choice of options.
The time of the shutdown and the warning message are placed in /etc/nologin and should be used to tell the users why the system is going
down, when it will be back up, and to share any other pertinent information.
FILES
/etc/nologin tells login(1) not to let anyone log in
/fastboot tells rc(8) not to run fsck(8) when rebooting
/etc/rc.shutdown System shutdown commands
SEE ALSO
login(1), wall(1), fastboot(8), halt(8), init(8), poweroff(8), reboot(8), rescue(8)
BACKWARD COMPATIBILITY
The hours and minutes in the second time format may be separated by a colon (``:'') for backward compatibility.
HISTORY
The shutdown command appeared in 4.0BSD.
BSD
October 4, 2011 BSD