or you could just let the script sleep every 5 seconds ... start it from cron every start of the hour ... script sample below wil exit if $lockfile exists ... removing lockfile will kill running script ...
Code:
#! /bin/ksh
lockfile=/tmp/lockfile
repeatJob(){
echo "boo"
echo "duh\n"
if [ ! -f $lockfile ]
then
break
else
sleep 5
repeatJob
fi
}
if [ ! -f $lockfile ]
then
touch $lockfile
repeatJob
else
echo "$lockfile exists. Exiting."
exit 1
fi
exit 0
I scheduled 2 Oracle jobs to run on IBM AIX 4.3.3 at
06:50 and 06:58 on 02/02/03 with the below syntax:
$ at 06:50 02/02/03 /orac/ora11/temp/sun_job1.sh
Job oracle.1044175800.a will be run at Sun Feb 2 06:50:00 2003.
$ at 06:58 02/02/03 /orac/ora11/temp/sun_job2.sh
Job... (1 Reply)
Hello,
I want to know about job scheduling utilities available in unix. It should not be responsible just for starting the job like in case of cron but should also be able to handle the execution of jobs.
Regards,
Ritesh (1 Reply)
I am working on UNIX AIX system, with Oracle OS.
We are not supposed to use any tools to schedule our unix shell scripts.
Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc.
If anyone has worked/ is working... (1 Reply)
I am working on UNIX AIX system, with Oracle OS.
We are not supposed to use any tools to schedule our unix shell scripts.
Basically we have to make use of Oracle tables and Shell scripts to manage dependencies, restartability, scheduling, parallelizing,etc.
If anyone has worked/ is working... (4 Replies)
Hello All,
I want to run a script for every 5 minutes interval.So i developed a script which has to be scheduled to run for every 5 minutes. That script internally runs another script. But the problem is it is not executing properly. Can anybody throw some light on this.
Below are the code... (4 Replies)
Hi All,
I have a script which is scheduled in the Cron. It runs every 10th and 40th min of an hour.The job has to run every 30min.
But, I do not want to have the 00:10 MST run every day.Is it possible to exclude that run from the schedule?Or any other way through which i can run my job every... (4 Replies)
Hi All,
I've been trying to schedule a job using the at command on Solaris 5.10 but i've been running into some issue. ( Not allowed to use cron :wall: )
I have a script that reads a logs file, does some iteration and cat's the output in an email .
## the o/p of /home/myscript.sh is : ... (2 Replies)
Hi All,
I am new to unix and i have a task in front of me.
The code part is "android update sdk" . I need to crontab this process.
Hence i have written a script that runs the above command and sends a mail once the update is done. The problem with the automation is the installer asks for a... (5 Replies)
Discussion started by: Kashyap
5 Replies
LEARN ABOUT DEBIAN
lockfile-progs
lockfile-progs(1) Lockfile programs lockfile-progs(1)NAME
lockfile-progs - command-line programs to safely lock and unlock files and mailboxes (via liblockfile).
SYNOPSIS
mail-lock [--use-pid] [--retry retry-count]
mail-unlock
mail-touchlock [--oneshot]
lockfile-create [--use-pid] [--retry retry-count] [--lock-name] filename
lockfile-remove [--lock-name] filename
lockfile-touch [--oneshot] [--lock-name] filename
lockfile-check [--use-pid] [--lock-name] filename
DESCRIPTION
Lockfile-progs provides a set a programs that can be used to lock and unlock mailboxes and files safely (via liblockfile):
mail-lock - lock the current user's mailbox
mail-unlock - unlock the current user's mailbox
mail-touchlock - touch the lock on the current user's mailbox
lockfile-create - lock a given file
lockfile-remove - remove the lock on a given file
lockfile-touch - touch the lock on a given file
lockfile-check - check the lock on a given file
By default, the filename argument refers to the name of the file to be locked, and the name of the lockfile will be filename .lock. How-
ever, if the --lock-name argument is specified, then filename will be taken as the name of the lockfile itself.
Each of the mail locking commands attempts to lock /var/spool/mail/<user>, where <user> is the name associated with the effective user ID,
as determined by via geteuid(2).
Once a file is locked, the lock must be touched at least once every five minutes or the lock will be considered stale, and subsequent lock
attempts will succeed. Also see the --use-pid option and the lockfile_create(3) manpage.
The lockfile-check command tests whether or not a valid lock already exists.
OPTIONS -q, --quiet
Suppress any output. Success or failure will only be indicated by the exit status.
-v, --verbose
Enable diagnostic output.
-l, --lock-name
Do not append .lock to the filename. This option applies to lockfile-create, lockfile-remove, lockfile-touch, or lockfile-check.
-p, --use-pid
Write the parent process id (PPID) to the lockfile whenever a lockfile is created, and use that pid when checking a lock's validity.
See the lockfile_create(3) manpage for more information. This option applies to lockfile-create and lockfile-check. NOTE: this option
will not work correctly between machines sharing a filesystem.
-o, --oneshot
Touch the lock and exit immediately. This option applies to lockfile-touch and mail-touchlock. When not provided, these commands will
run forever, touching the lock once every minute until killed.
-r retry-count, --retry retry-count
Try to lock filename retry-count times before giving up. Each attempt will be delayed a bit longer than the last (in 5 second incre-
ments) until reaching a maximum delay of one minute between retries. If retry-count is unspecified, the default is 9 which will give
up after 180 seconds (3 minutes) if all 9 lock attempts fail.
EXAMPLES
Locking a file during a lengthy process:
lockfile-create /some/file
lockfile-touch /some/file &
# Save the PID of the lockfile-touch process
BADGER="$!"
do-something-important-with /some/file
kill "${BADGER}"
lockfile-remove /some/file
EXIT STATUS
0
For lockfile-check this indicates that a valid lock exists, otherwise it just indicates successful program execution.
Not 0
For lockfile-check a non-zero exit status indicates that the specified lock does not exist or is not valid. For other programs it
indicates that some problem was encountered.
SEE ALSO maillock(3)touchlock(3)mailunlock(3)lockfile_create(3)lockfile_remove(3)lockfile_touch(3)lockfile_check(3)AUTHOR
Written by Rob Browning <rlb@defaultvalue.org>
0.1.12 2008-02-10 lockfile-progs(1)