On 17/06/04, Edmund Bacon (ebacon@onesystem.com) wrote:
> Rory Campbell-Lange wrote:
>
> > I am in a dilemma about how best to pick up these messages and send them
> > on to the message sending systems. At present I have looping perl
> > scripts which have a permanent database connection, which I run through
> > screen sessions on my server. Rather embarassingly whenever I upgrade my
> > application code (reload the database and export the latest CVS code) or
> > upgrade Postgres, my looping scripts die.
> Assuming you are on a unix of some sort, Two possible solutions come
> immediately to mind.
>
> 1) Fire off a non-looping version of your perl scrip from crontab
>
> 2) Run your looping perl script from the inittab.
>
> the crontab solution would be my preference: it's easier to set up the job
> to run under a user other than root, and you can tailor when your script
> runs (say every 5 minutes between 8:00 AM and 6:00 PM Monday to Friday).
I should have mentioned that we need the messages sent very soon after
they have landed in the 'inbox'; otherwise cron would definitely be the
way to go -- including an @reboot line.
Thanks for the suggestion, though.
Rory
--
Rory Campbell-Lange
<rory@campbell-lange.net>
<www.campbell-lange.net>
