02-15-2009
basically to schedule a cron job, just need to ensure the script with path is executable, test to run it manually with right account. Then schedule in crontab and monitor the cron log (eg. /var/log/cron) depend on which unix platform...
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all
we r using hpUX11.00 9000 sever as oracle 8i db server...
But the problem is we have 4 instances of dbs but upto my knowledge there are only to ports available for TNS listen...
how can i configure or get wht ever it may be the other two ports for tns listener.........
... (2 Replies)
Discussion started by: Prafulla
2 Replies
2. Shell Programming and Scripting
this is my lex file ------------ test.l
%%
printf("%c",yytext+'a'-'A');.ECHO;
how do i compile it
$ lex test.l cc lex.yy.c -o test -ll <------|
|
if this is correct do i add this line--------| @the command line or does it... (0 Replies)
Discussion started by: sinner
0 Replies
3. UNIX for Dummies Questions & Answers
need help....just wanna copy all files with no extensions but with tree-informations to one dir
first I make a new directory with all foldertrees...like
find / -name "*" -type d >a1
sed -e 's/^/new/g' <a1 >b1
mkdir -p `cat a1`
then I wanna copy all specific files with no... (12 Replies)
Discussion started by: svennie
12 Replies
4. Solaris
Server 1 SSH Version Sun_SSH_1.0
Server 2 OpenSSH_3.8.1p1
Server 3 OpenSSH_3.8p1
I created the rsa keys on server1. Public and private. I copied the id_rsa.pub file to server2 and server3 and appended this to the authorized_keys file in the .ssh directory on both. (All servers using the root... (2 Replies)
Discussion started by: frustrated1
2 Replies
5. Shell Programming and Scripting
I do not have the luxery of a server that i can try on, so i had to post my qn here.
Say i have two jobs in the cron table, the jobs are scheduled 2 mins apart. Assuming the first jobs does a lot of operations and takes > 2 mins. Will the second job be executed? Will Unix actually have a queue... (3 Replies)
Discussion started by: new2ss
3 Replies
6. Shell Programming and Scripting
Hi
I have written a shell script(in Solaris) in which following logic is there.....
i=1
while read control
do
key=`echo $control | awk -F$DELIMITOR '{ print $1 }'`
echo "Key Values" ${key}
i=`/usr/bin/expr $i + 1`
done < $CONFPATH/$CONFFILE
when i execute it at prompt it... (4 Replies)
Discussion started by: Amardeep
4 Replies
7. UNIX for Advanced & Expert Users
Hi,
if I launche this at commande line It is OK :
$ /home/oracle/anaschxt_A01_5_15_25_plemae.sh
but if I put it in crontab :
Like this :
I have this error :
/home/oracle/anaschxt_A01_5_15_25_plemae.sh: sqlplus: not find.
The script is :
+17 ... (2 Replies)
Discussion started by: big123456
2 Replies
8. UNIX for Dummies Questions & Answers
hi guys...
i m using rm *.zip or rm -rf *.zip while removing from a server path recursively,
i m getting "Remove directory operation failed."
if i use rm* .zip
i m getting as invalid command and none of the files are removed..
please help where m i wrong
when i execute the... (13 Replies)
Discussion started by: madhu_aqua14
13 Replies
9. Shell Programming and Scripting
Hi,
I have written a script for file scan :
#!/bin/sh
find . -name "common.log.diff" > /dev/null 2>&1
if ; then
cp common.log common.log.diff
diff common.log common.log.diff > DIFFERENCE.log
cp common.log common.log.diff
grep "ERROR" DIFFERENCE.log
if ; then
echo "1" >... (6 Replies)
Discussion started by: himvat
6 Replies
10. Debian
Hi all
I installed Debian and i have a few scripts that outputs what is happening.
The wierd part...after fresh install all works ok but after i open or edit Crontab it stops executing the scripts...and scripts runs manually so its not a problem with scripts...what happens is that i usually... (3 Replies)
Discussion started by: ro0t3d
3 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (Vixie Cron)
SYNOPSIS
cron [-s] [-o] [-x debugflag[,...]]
DESCRIPTION
The cron utility is launched by launchd(8) when it sees the existence of /etc/crontab or files in /usr/lib/cron/tabs. There should be no
need to start it manually. See /System/Library/LaunchDaemons/com.vix.cron.plist for details.
The cron utility searches /usr/lib/cron/tabs for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into
memory. The cron utility also searches for /etc/crontab which is in a different format (see crontab(5)).
The cron utility then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current
minute. When executing 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 modification time (or the modification time on /etc/crontab) has
changed, and if it has, cron will then examine the modification time 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 modification time of the spool directory
whenever it changes a crontab.
Available options:
-s Enable special handling of situations when the GMT offset of the local timezone changes, such as the switches between the standard
time and daylight saving time.
The jobs run during the GMT offset changes time as intuitively expected. If a job falls into a time interval that disappears (for
example, during the switch from standard time) to daylight saving time or is duplicated (for example, during the reverse switch),
then it is handled in one of two ways:
The first case is for the jobs that run every at hour of a time interval overlapping with the disappearing or duplicated interval.
In other words, if the job had run within one hour before the GMT offset change (and cron was not restarted nor the crontab(5)
changed after that) or would run after the change at the next hour. They work as always, skip the skipped time or run in the added
time as usual.
The second case is for the jobs that run less frequently. They are executed exactly once, they are not skipped nor executed twice
(unless cron is restarted or the user's crontab(5) is changed during such a time interval). If an interval disappears due to the GMT
offset change, such jobs are executed at the same absolute point of time as they would be in the old time zone. For example, if
exactly one hour disappears, this point would be during the next hour at the first minute that is specified for them in crontab(5).
-o Disable the special handling of situations when the GMT offset of the local timezone changes, to be compatible with the old (default)
behavior. If both options -o and -s are specified, the option specified last wins.
-x debugflag[,...]
Enable writing of debugging information to standard output. One or more of the following comma separated debugflag identifiers must
be specified:
bit currently not used
ext make the other debug flags more verbose
load be verbose when loading crontab files
misc be verbose about miscellaneous one-off events
pars be verbose about parsing individual crontab lines
proc be verbose about the state of the process, including all of its offspring
sch be verbose when iterating through the scheduling algorithms
test trace through the execution, but do not perform any actions
FILES
/usr/lib/cron/tabs Directory for personal crontab files
SEE ALSO
crontab(1), launchctl(1), crontab(5), launchd.plist(5), launchd(8)
AUTHORS
Paul Vixie <paul@vix.com>
BSD
June 17, 2007 BSD