Assuming that you have good reason to keep your job2 separate from job1 (maybe you don't own job1 and the owner doesn't want you piggybacking on it), perhaps job1 could create a trigger file for your job2.
Set your job2 in cron to run every hour (or whatever). The first thing you do is look for the file created by the completion of job1, if no file... exit(0). If you find a file, remove it and begin processing. If you don't remove it first, depending on the length of your job, cron might cause you to run again if you let the file sit. This is less appealing than the first couple of suggestions you received as far as simplicity goes, but it does decouple the two jobs which has its' benefits depending on your environment. Bryan -----Original Message----- From: Thomas_M [mailto:[EMAIL PROTECTED]] Sent: Tuesday, February 12, 2002 9:06 AM To: 'AITHA, BHEEMSEN (SBCSI)'; '[EMAIL PROTECTED]' Subject: RE: [Perl-unix-users] How to make a job dependent on another AITHA, BHEEMSEN (SBCSI) [mailto:[EMAIL PROTECTED]] wrote: > I want to make my perl script job to be dependent on a > particular cron job. How do I do that ? What do you mean by dependent? Run immediately after the execution of a cron job? You can add your script to the same crontab as the existing job. Just separate it by a semicolon. _______________________________________________ Perl-Unix-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs _______________________________________________ Perl-Unix-Users mailing list [EMAIL PROTECTED] To unsubscribe: http://listserv.ActiveState.com/mailman/mysubs
