Another approach is to use the Shell's own background job management and handle the whole lot in one controlling script called from one cron.
This example runs "ls" 10 times concurrently in background, waits until all 10 jobs have finished, then checks for 10 success flag files.
Code:
ls >/tmp/success1 &
ls >/tmp/success2 &
ls >/tmp/success3 &
ls >/tmp/success4 &
ls >/tmp/success5 &
ls >/tmp/success6 &
ls >/tmp/success7 &
ls >/tmp/success8 &
ls >/tmp/success9 &
ls >/tmp/success10 &
#
# Sleep until all 10 background jobs finish
while true
do
[ ! "`jobs`" ] && break
sleep 10
done
#
# Check success flags
if [ -f /tmp/success1 -a -f /tmp/success2 -a -f /tmp/success3 \
-a -f /tmp/success4 -a -f /tmp/success5 -a -f /tmp/success6 \
-a -f /tmp/success7 -a -f /tmp/success8 -a -f /tmp/success9 \
-a -f /tmp/success10 ]
then
echo "11th job goes here"
else
echo "One or more jobs failed"
fi
i have tried to schedule my process at a certain time using the at command :
the error says bad time specification
can somebody help me
i used at 2300 job
thanks (2 Replies)
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 !!!
i am trying to create a command scheduler (written in C).
Basically i would like to do what the "at" command does , but without using "at" or "cron".
I have tried using getitimer but i do not know how can i shcedule multiple commands.
Any ideas ??? (2 Replies)
Hi Everybody,
How to schedule a job using cron that shouldn't run between working hrs 9am-5pm, while run in non working hrs every hour, every day of the month, month & week.
I tried the following way, not sure I can use logical not operator(!). Please correct me if wrong or suggest other... (2 Replies)
Hi all,
My OS is Solaris 10. I want to schedule a job which i need to run between morining 6 to eve 6 once for every 2 hours. This is what i did.
0 6-18 * * 1-5 /monitor.sh
It runs for every hour how to make it for every two hours ......
Thanks,
Firestar. (1 Reply)
hi
I have a script, abc.sh
first time user will start a script using <<abc.sh start >>, inside a script using " at " i am schduling same script for every one hour. so my script always running .
total script execution time takes around 1sec
for closing same << abc.sh stop>>
here... (2 Replies)
I AM ON SOLARIS
I have a script it.sh which is running fine when i execute it from shell command.
But when i schedule it in crontab it is throwing error.
Why and how can i resolve it ?i am clueless
IT.SH
#!/bin/sh
ORACLE_HOME=/var/opt/oracle/product/10g; export ORACLE_HOME... (1 Reply)
Hi,
I have my script in below path in UNIX
/storage/sas_source/SDTM-Development/FileWatcher/filewatcher.sh
I want to schedule it to run every 30 secs.
Please let me know the steps to do it.
Thanks. (7 Replies)
Discussion started by: prats_7678
7 Replies
LEARN ABOUT V7
dh_movefiles
DH_MOVEFILES(1) Debhelper DH_MOVEFILES(1)NAME
dh_movefiles - move files out of debian/tmp into subpackages
SYNOPSIS
dh_movefiles [debhelperoptions] [--sourcedir=dir] [-Xitem] [file...]
DESCRIPTION
dh_movefiles is a debhelper program that is responsible for moving files out of debian/tmp or some other directory and into other package
build directories. This may be useful if your package has a Makefile that installs everything into debian/tmp, and you need to break that
up into subpackages.
Note: dh_install is a much better program, and you are recommended to use it instead of dh_movefiles.
FILES
debian/package.files
Lists the files to be moved into a package, separated by whitespace. The filenames listed should be relative to debian/tmp/. You can
also list directory names, and the whole directory will be moved.
OPTIONS --sourcedir=dir
Instead of moving files out of debian/tmp (the default), this option makes it move files out of some other directory. Since the entire
contents of the sourcedir is moved, specifying something like --sourcedir=/ is very unsafe, so to prevent mistakes, the sourcedir must
be a relative filename; it cannot begin with a `/'.
-Xitem, --exclude=item
Exclude files that contain item anywhere in their filename from being installed.
file ...
Lists files to move. The filenames listed should be relative to debian/tmp/. You can also list directory names, and the whole directory
will be moved. It is an error to list files here unless you use -p, -i, or -a to tell dh_movefiles which subpackage to put them in.
NOTES
Note that files are always moved out of debian/tmp by default (even if you have instructed debhelper to use a compatibility level higher
than one, which does not otherwise use debian/tmp for anything at all). The idea behind this is that the package that is being built can be
told to install into debian/tmp, and then files can be moved by dh_movefiles from that directory. Any files or directories that remain are
ignored, and get deleted by dh_clean later.
SEE ALSO debhelper(7)
This program is a part of debhelper.
AUTHOR
Joey Hess <joeyh@debian.org>
11.1.6ubuntu2 2018-05-10 DH_MOVEFILES(1)