As a quick first pass, I'd suggest that your line that ends with || exit -1 & will actually put an exit -1 into the background if the data_process call fails (returns non-zero) but doesn't cause the overall call to data_process code to run in the background.
Have I got that wrong?
You might want this:-
It might be simpler to have a directory called 'Running' that you create a marker file in when you start a job and only remove when you successfully exit. That way, you could write something to read the directory contents for a restart.
Hi All,
I am working on solaris 8 sparc machine with 2 cpu.
I am trying to run my application which generates files. I run multiple instance of the application, but the results don't seem to show as if it were runing parallely.
When i run the application once it takes 12 secs to generate a... (1 Reply)
Hi
I want to run two shell script files parallely. These two scripts are interacting with the database. can any body help on this Pls
Regards
Audippa naidu.M (3 Replies)
Hi
I am looking for some kind of feature in unix that will help me write a script that can invoke multiple processes in parallel. And make sure that the multiple parallel processes complete successfully before I proceed to the next step.
Someone suggested something called timespid or... (6 Replies)
hi i am preparing a set of batches for a set of files sequentially
There is a folder /xyz where all the files reside
now all the files starting with
01 - will be appended for one below other to form a batch batch01
then all the files starting with
02 - will be appended for one below other to... (7 Replies)
Hello everybody,
I have a little problem with one of my program. I made a plugin for collectd (a stats collector for my servers) but I have a problem to make it run in parallel.
My program gathers stats from logs, so it needs to run in background waiting for any new lines added in the log... (0 Replies)
Hello
I have a shell script with multiple sections in it. Like, verify pre-requisites, ch co version, stop services , install product , post migration steps, start services, send status email.
If the script fails at certain step, (like after product installation) it can't be re-run since the... (2 Replies)
I have 10,000 + files, each of which I need to zip using bzip2.
Is ti possible to use bash to create 8 parallel streams sending a new file to be processed from the list when one of the others has finished? (1 Reply)
Discussion started by: garethsays
1 Replies
LEARN ABOUT CENTOS
repodiff
repodiff(1)repodiff(1)NAME
repodiff - list differences between two or more Yum repositories
SYNOPSIS
repodiff --old=old_repo_baseurl --new=new_repo_baseurl
DESCRIPTION
repodiff is a program which will list differences between two sets of repositories. Note that by default only source packages are com-
pared.
GENERAL OPTIONS --old, -o
Add a repo. as an old repo. Note that if you prefix the url with "mirror:" then the following url is treated as a mirror and not a
baseurl.
--new, -n
Add a repo. as an new repo. Note that if you prefix the url with "mirror:" then the following url is treated as a mirror and not a
baseurl.
--archlist, -a
Add architectures to change the default from just comparing source packages. Note that if you want the same as a native "x86_64"
architecture machine you just need to pass "x86_64" (this is different from earlier versions where you needed to specify
"x86_64,athlon,i686,i586,i486,i386,noarch" and you still got "src").
--size, -s
Output additional data about the size of the changes.
--compare-arch
Normally packages are just compared based on their name, this flag makes the comparison also use the arch. So foo.i386 and
foo.x86_64 are different.
--simple
Output a simple one line message for modified packages.
--downgrade
Split the data for modified packages between upgraded and downgraded packages.
EXAMPLES
Compare source pkgs in two local repos:
repodiff --old=/tmp/repo-old --new=/tmp/repo-new
Compare x86_64 compat. binary pkgs in two remote repos, and two local one:
repodiff -a x86_64 --old=http://example.com/repo1-old --old=/tmp/repo-old --new=http://example.com/repo1-new --new=/tmp/repo-new
Compare x86_64 compat. binary pkgs, but also compare arch:
repodiff -a x86_64 --compare-arch --old=http://example.com/repo1-old --old=/tmp/repo-old --new=http://example.com/repo1-new
--new=/tmp/repo-new
Compare two releases of Fedora (15 => 16):
repodiff --old='mirror:https://mirrors.fedoraproject.org/metalink?repo=fedora-source-15&arch=i386' --new='mirror:https://mir-
rors.fedoraproject.org/metalink?repo=fedora-source-16&arch=i386' --size --simple --downgrade
SEE ALSO
yum.conf (5)
http://yum.baseurl.org/
AUTHORS
See the Authors file included with this program.
BUGS
There are of course no bugs, but should you find any, you should first consult the FAQ section on http://yum.baseurl.org/wiki/Faq and if
unsuccessful in finding a resolution contact the mailing list: yum-devel@lists.baseurl.org. To file a bug use http://bugzilla.redhat.com
for Fedora/RHEL/Centos related bugs and http://yum.baseurl.org/report for all other bugs.
James Antill 21 October 2008 repodiff(1)