that is how i have it set up. first, a vacuum. next line in the script is
a "select. . .not in" query that takes forever. cron executed the first
(the vacuum) and then immediatly executed the second (the select), so both
the vacuum and the select were running at the same time. needless to say
they were still running when our morning crew arrived, and all were locked
out of the system until i killed everything!
jt
-----Original Message-----
From: Hitesh Patel [SMTP:[EMAIL PROTECTED]]
Sent: Tuesday, September 28, 1999 11:14 AM
To: JT Kirkpatrick
Cc: '[EMAIL PROTECTED]'
Subject: Re: [ADMIN] sequence of commands -- waiting on the first to
complete!
JT Kirkpatrick wrote:
>
> i'm trying to run a query at night, and output the results to a file. i
> think i have the syntax right for the proper output, but it now appears
> that my little automatic (cron) query ran IMMEDIATELY after the first
> command in the same cron file (a VACUUM of the same database) executed.
it
> didn't wait until it was finished. besides guessing what time the vacuum
> will be complete, and scheduling the second command in a separate cron
> appropriately timed to run afterwards, is there a way to "stream" the two
> commands such that the second does NOT execute until the first one is
> complete??
>
> thanks! jt
>
> ************
Put your commands in a shell script somewhere in the order you want them
to execute and then tell cron to run that shell script.
--
|---------------------------------|----------------------------|
| Hitesh Patel | Voice: (541) 759-3126 |
| Facilities Development Manager | Fax: (541) 759-3214 |
| Preferred Systems | Email: [EMAIL PROTECTED] |
|---------------------------------|----------------------------|
************
