Will, Good call on lockrun, I usually code something into my jobs to ensure they don't run concurrently, by checking if a script with the same name is already running, and throwing an error condition.
Lockrun seems smart enough though. - Lee 2009/7/6 Will Jessop <[email protected]> > > On 6 Jul 2009, at 12:18, Adrian McEwen wrote: > > doug livesey wrote: > >> Hi -- millions of years ago (or thereabouts), I seem to remember > >> hearing that if you put a "puts" in a task you were going to schedule > >> in a cron job to run as a daemon, that could cause issues. > >> Has anyone found this? > >> Or did I dream it? > >> Because I want to do that very thing in a rake task I'm going to be > >> scheduling. > >> Cheers, > >> Doug. > > I've never had any problems with that - I've got plenty of rake tasks > > run over cron that use puts to provide some output information. Cron > > gathers the output into an email and sends it to whoever owns the cron > > job once the job completes. IIRC you can choose a different email > > address, it's just a case of reading up on how cron works. > > > Yup, just stick: > > MAILTO=your address > > above the jobs you want to receive the output from. Also, if you're > running anything intense/regularly you should really use something > like lockrun (http://unixwiz.net/tools/lockrun.html) to prevent > overrun, swapping and untimely server death. > > Will. > > -- > Will Jessop > Super Shiny Robot Limited - Professional web design and development > > t: 07939 547 962 > w: http://supershinyrobot.com/ > > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "NWRUG" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nwrug-members?hl=en -~----------~----~----~----~------~----~------~--~---
