12-17-2007
Thanks Porter
Quote:
Originally Posted by
porter
Each user gets a crontab, each crontab can have a number of entries.
Each entry has a date/time specification and a command to run.
Only one cron process is required, it spawns child processes and runs the commands as required.
Hi Porter,
Thanks for your reply.
10 More Discussions You Might Find Interesting
1. HP-UX
This isn't the usual problem that a shell script runs from the command line and not the cron. It's a little different.
Among other things, the shell scrip executes my .profile to set a bunch of variables. It then does an env to ensure that it ran OK.
There are echos in the shell script and... (2 Replies)
Discussion started by: abNORMal
2 Replies
2. Shell Programming and Scripting
Hi everybody!
I'm struggling against a script that won' t work right in a cron job
this is my script:
cat serverlist | while read arg
do
if
then
echo "$arg"
ping -c 4 $arg >> /dev/null
if
then
... (3 Replies)
Discussion started by: deppy82
3 Replies
3. Shell Programming and Scripting
Hi Guys,
Unable to run this script from the cron,although the same executes perfectly from the command line.Please help.
#!/bin/sh
#### aprintd alarm creation files #####
file=`date +%m%d%Y`
pid=$$
echo "$pid"
/u01/app/netboss/bin/aprintd/aprintd > $file &
childpid=$!... (3 Replies)
Discussion started by: ashish.sharma
3 Replies
4. Shell Programming and Scripting
Hey Guys,
i was trying out a shell script which has to remove a file for every 90 mins. this is the code i came up with .
$ crontab -e file1
file1 contains
30 1 * * * * rm -r /folder1/folder2/somefile.txt
Now i need the cron to run for every 90 mins. the problem with this is... (8 Replies)
Discussion started by: Irishboy24
8 Replies
5. Shell Programming and Scripting
Hello,
I know little about shell scripting and creating a script, and worked fine in the command line. But not work in the cron. Below you could see the script
#!/bin/sh
LOGFILE=/home/transfield/mou/test.log
# Find yesterday Date and copy files
TODAY=$(date --date= +%F)
YESTERDAY=$(date... (4 Replies)
Discussion started by: malikp
4 Replies
6. Shell Programming and Scripting
Hi there,
I have a script that pulls in a weather feed via FTP then writes the output to a file.
This script is run everyday at 3pm by cron.
Heres the shell script:
#!/bin/sh
HOST='ftp.weatheronline.co.uk'
USER='my username'
PASSWD='my password'... (2 Replies)
Discussion started by: mpk_3
2 Replies
7. Shell Programming and Scripting
Hi guys,
I have a serious issue with running cron command. My host not supported format below mentioned, just the URL.) http://www.mysite/example.php ( I’m affraid a bit, the host do not going to support the sh as well…anyway)
Somehow I need to „wrap” this command, to able to call cron:
... (1 Reply)
Discussion started by: vazzeg
1 Replies
8. Shell Programming and Scripting
How can I tell a script to only execute if the other scripts exits successfully?
So "script A" executes and if it executes successfully (0),then "script B" will run
or else
"script A "executes and it exits unsucessfully (1) then "script B" will read return code (1) and will not execute
... (3 Replies)
Discussion started by: metallica1973
3 Replies
9. UNIX for Dummies Questions & Answers
Hi all, hopefully someone out there can give me some tips on how to resolve this
I have a simple shell script
who -u > /tmp/userlog
one of the line stored in userlog when executing shell script manually:
jim123 pts/24 2012-03-30 13:02 00:56 4131 (xya.dsfgds.com)
one of the... (4 Replies)
Discussion started by: Linux_Novice
4 Replies
10. AIX
We run some menu driven software that has the ability to batch menu paths and generate reports quickly. Normally you run a batch like:
$ BATCH BATCHNAME
The batch program then prompts you for the date you want the report run for. I got some help from some folks on IRC to do the following:
BATCH... (2 Replies)
Discussion started by: herot
2 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)