Good call will, hadn't really thought of it so granularly - I suppose if I don't have the cpu time and memory space to bring up a ruby thread my server is already in trouble! - Lee
2009/7/6 Will Jessop <[email protected]> > > On 6 Jul 2009, at 12:36, Lee Hambley wrote: > > 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. > > > lockrun has the advantage of being written in c and so being tiny and > fast. I have used 'lockfile' before ( > http://raa.ruby-lang.org/project/lockfile/ > ) but any solution that loads ruby into memory before it determines > whether it should be running or not is going to lose that edge in low > memory situations or where the server is swapping. > > 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 -~----------~----~----~----~------~----~------~--~---
