01-08-2008
Right, so i have got it to work, only by actually inputting every time i want it to run into the crontab, but now the next problem is that it wont do a clean shutdown
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Dear all
I would like to shutdown multiple servers remotely with the issue of one single command. What is the command to shut down a server remotely (ie, I want to issue a command on server X to shutdown server Y and server Z).
Thank you (2 Replies)
Discussion started by: soliberus
2 Replies
2. UNIX for Advanced & Expert Users
Hi Guys,
I want to execute few of my bash script, so that whenever someone calls shutdown now -r command, I want my script to execute first before shutting down.
Any help please?????
I've just started playing with the unix system, so far its been brilliant.... (10 Replies)
Discussion started by: alpha_manic
10 Replies
3. Shell Programming and Scripting
hi all,
Im fairly new to scripting and am having a noobish issue. Ive got a script that checks for certain directories and if they dont exist, prompts the user to do a mkdir. heres trouble spot in the script:
cat dirlsttemp.dat | while read dir; do
echo "$dir does not exist, would you... (3 Replies)
Discussion started by: rdudejr
3 Replies
4. UNIX for Dummies Questions & Answers
I want to make a script to shutdown a unixware computer from other user then root. In Sco version i use "as root" but in the unixware i don't know.
Please help me.
10x (12 Replies)
Discussion started by: kelu
12 Replies
5. HP-UX
Hi,
I am on Alpha Server with HP Tru64 system.
I wish to setup shutdown to automatically and cleanly shutdown informix during the shutting down of the system.
Ie. I was trying to use rc0.d to do this but failed.
Has anyone tried doing this before? I already have the script and linked it
to... (0 Replies)
Discussion started by: kingsto88
0 Replies
6. Shell Programming and Scripting
Hi, i need shutdown a pc, is in the same network
what command i can use in the script :o ? (1 Reply)
Discussion started by: Dymblos
1 Replies
7. 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
8. Shell Programming and Scripting
Im writing a script to read a file called shutdown.cf and shut down any scripts that are listed there.
I have came up with the following based on things I saw in similar programs but it doesn not work:
Has anybody any idea what I may be doing wrong?
Cheers
Paul (4 Replies)
Discussion started by: runnerpaul
4 Replies
9. Shell Programming and Scripting
Hi All,
I'm a newbie here.. how can i grep the data when i receive responce from TL1
example:
responce from TL1:
blabalbalbalbalba.,lbalba,SUCCESFULL,blahblahbalabh... how can i grep the "SUCCESSFULL" while i'm running the script? is it possible? because i'm only to know is if... (2 Replies)
Discussion started by: nikki1200
2 Replies
10. Shell Programming and Scripting
I am going to create shutdown database script. We have dabase shutdown script.
But i need take dabase which online and make it down.
I got user id which needs to dabase to down
ID=`ps -ef | grep -i pmon | grep -v grep | awk '{print $1}'` (
got orace side
DB=`ps -ef | grep -i pmon |... (1 Reply)
Discussion started by: allwin
1 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). Cron then
wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When execut-
ing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab, if
such exists).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) has changed, and if it has,
cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if
time has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO
crontab(1), crontab(5), pam(8)
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)