> > I use Jobs MaxServers 1 and I have a quick job that runs every 15 > > minutes and some longer jobs that run once a day. Whenever one of > > these longer jobs runs, the jobs queue fills up with the quick jobs. > > How do you guys deal with that? > > Why don't you use Jobs MaxServers 2 in that case ? When I'm writing a job I like knowing that another job won't be changing data at the same time as the one I'm writing. It keeps things sane. What would be really handy is something like: --runjobs=catname=jobname=noqueue - Grant _______________________________________________ interchange-users mailing list suppressed http://www.icdevgroup.org/mailman/listinfo/interchange-users
Mail converted by mhonarc 2.6.15
This archive provided courtesy of JSW4.NET, Internet Hosting Services for Small Business.