Retry Logic But In Cron Post: 303046120

Sponsored Content

Top Forums UNIX for Beginners Questions & Answers Retry Logic But In Cron Post 303046120 by jgt on Friday 24th of April 2020 10:58:49 AM

04-24-2020

Registered User

In the following, the index file is placed in the requests directory, and the image file in the temp directory. The index files can have different extensions to indicate grouping or priority.
The pid file is used to prevent subsequent invocations of the cron job from running.
You can periodically examine the contents of the temp and request directories for entries that older than some specified time.

Code:

#!/bin/ksh
cd /u/email
BATCH=$1
proc=$$
if [ -r /u/email/$BATCH.pid ]
then
    echo "Previous batch  still running" $(cat $BATCH.pid)
    exit
fi
echo $proc >/u/email/$BATCH.pid
list=$(ls requests|grep $BATCH)
if [ "$list" != "" ]
    then
    for request in $list
    do
    #do processing here          
    #if successful 
        mv requests/$request done
        mv temp/$request* done
    #else
       #echo "This one failed"
       #fi
    done
fi
rm /u/email/$BATCH.pid
echo finished at $(date)

jgt

View Public Profile for jgt

Visit jgt's homepage!

Find all posts by jgt

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Retry upon FTP failure

I am using the following code in a C Shell script to transfer files to a remote server: ftp -n logxx.xxxx.xxx.xxx.com <<DO_FTP1 quote user $user_name quote pass $password ascii put $js_file_name bin put $FinalZipFile quit DO_FTP1 This code works great except on those rare occasions...

2. Shell Programming and Scripting

If then else - Retry operation

I need to read a file line by line, then depending on the contents of each line, type in a code that will get written to an array. The problem I have is when I ask the user to confirm the input code, if it is wrong, how do i Return to ask again? Any thing I try increments the file to the next...

LEARN ABOUT SUSE

cron

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)