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 MOJAVE

crontab

CRONTAB(1)						    BSD General Commands Manual 						CRONTAB(1)

NAME

     crontab -- maintain crontab files for individual users (V3)

SYNOPSIS

     crontab [-u user] file
     crontab [-u user] { -l | -r | -e }

DESCRIPTION

     The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron.  Each user
     can have their own crontab, and they are not intended to be edited directly.

     (Darwin note: Although cron(8) and crontab(5) are officially supported under Darwin, their functionality has been absorbed into launchd(8),
     which provides a more flexible way of automatically executing commands.  See launchctl(1) for more information.)

     If the /usr/lib/cron/cron.allow file exists, then you must be listed therein in order to be allowed to use this command.  If the
     /usr/lib/cron/cron.allow file does not exist but the /usr/lib/cron/cron.deny file does exist, then you must not be listed in the
     /usr/lib/cron/cron.deny file in order to use this command.  If neither of these files exists, then depending on site-dependent configuration
     parameters, only the super user will be allowed to use this command, or all users will be able to use this command.  The format of these
     files is one username per line, with no leading or trailing whitespace.  Lines of other formats will be ignored, and so can be used for com-
     ments.

     The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.

     The following options are available:

     -u      Specify the name of the user whose crontab is to be tweaked.  If this option is not given, crontab examines ``your'' crontab, i.e.,
	     the crontab of the person executing the command.  Note that su(1) can confuse crontab and that if you are running inside of su(1) you
	     should always use the -u option for safety's sake.

     -l      Display the current crontab on standard output.

     -r      Remove the current crontab.

     -e      Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables.  The specified editor must edit
	     the file in place; any editor that unlinks the file and recreates it cannot be used.  After you exit from the editor, the modified
	     crontab will be installed automatically.

FILES

     /usr/lib/cron/cron.allow
     /usr/lib/cron/cron.deny

DIAGNOSTICS

     A fairly informative usage message appears if you run it with a bad command line.

SEE ALSO

     crontab(5), compat(5), cron(8), launchctl(1)

STANDARDS

     The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'').  The new command syntax differs from previous versions of Vixie Cron, as well
     as from the classic SVR3 syntax.

AUTHORS

     Paul Vixie <paul@vix.com>

BSD
								 December 29, 1993							       BSD