10 More Discussions You Might Find Interesting
1. UNIX for Beginners Questions & Answers
Hi,
We have created a script that's checks the latency of IIDR subscription by fetching details from a config file (that contains subscription details) and running the CHCCLP command. The out put is then concatenated in a csv file. Once all subscription details are saved the script send a mail... (7 Replies)
Discussion started by: ab095
7 Replies
2. UNIX for Beginners Questions & Answers
i have written one script which is working fine when i run it manually but giving error when i schedule it in crontab.
cat SUMMARY.sh
#!/bin/bash
DT1=`date +%Y%m%d`
echo "Off PP TT" >>summary_$DT1.txt
cat ues1.txt_$DT1 >>summary_$DT1.txt
cat ues2.txt_$DT1... (2 Replies)
Discussion started by: scriptor
2 Replies
3. Shell Programming and Scripting
Hi Forum,
Good Day!
I have created an empty html file wtih permissoin 777
created shell script(with permission 777) , code is below.
#=======================start==============
. /data09/oracle/apps_st/appl/D_oraapp095.env
rm -rf /home/mnp/Test_log.txt
echo... (1 Reply)
Discussion started by: kartheekbk
1 Replies
4. Shell Programming and Scripting
i have a job scheduled in crontab. The problem is, it is not running automatically as per the time scheduled. But runs when executed manually. What would be the problem? Help me with this please. (6 Replies)
Discussion started by: Santhosh CJ
6 Replies
5. Red Hat
Hi all,
I'm working to a script with /bin/bash shebang.
The script works perfectly if I run from command line.
The script runs under a non root user and inside the commands are set with sudo command in a such a way they can be run under root, for example (first rows of the script):... (5 Replies)
Discussion started by: idro
5 Replies
6. UNIX for Dummies Questions & Answers
I have scheduled couple of shell scripts to run using 'at' command.
The o/p of at -l is:
$ at -l
1320904800.a Thu Nov 10 01:00:00 2011
1320894000.a Wed Nov 9 22:00:00 2011
1320876000.a Wed Nov 9 17:00:00 2011
$ uname -a
SunOS dc2prcrptetl2 5.9 Generic_122300-54 sun4u sparc... (2 Replies)
Discussion started by: superparticle
2 Replies
7. UNIX Desktop Questions & Answers
Hi,
I would like to master CRONTAB jobs in UNIX, can you please share more useful links and examples related to this, thank you. (1 Reply)
Discussion started by: Dev_Dev
1 Replies
8. UNIX for Dummies Questions & Answers
How would i run /usr/local/sbin/copyfile.sh at 8 p.m today.
What should i write in crontab -e ? (4 Replies)
Discussion started by: pinga123
4 Replies
9. Shell Programming and Scripting
Hi All,
I have written a script which checks for the quota of the system and sends the mail to the user if quota increases a particular threshold.
I want that this scripts get automaticaaly executed ,whic h I believe can be done with the help of crontab.
I am unaware of how to use this crontab.... (11 Replies)
Discussion started by: Taranjeet Singh
11 Replies
10. 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
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