Cronjobs in different queues

[Gert Svedvall]

Is ther a way to direct job's run from crontab to another queue then to C?
Is it possible to specify the -q parameter in the commandstring?

[Massimo Bianchi]

Hi,
i think you have to play with

queuedefs

to get it right, but i do not imagine how...

HTH,
Massimo

[Thierry Poels_1]

Hi,

the cron queue is the c queue.

No other options. A possible workaround is to start at jobs in a specific queue from the cron. Only the atjob will be launched then from the c queue, the atjob itself will run then in the specified queue.

regards,
Thierry.

[Gert Svedvall]

I have 5 at-jobs and no batchjobs and as I understand it i should be able to have 95 crontabjobs but the message :
a queue max run limit reached
appears quite frequently in the cronlog,
how come?
The crontab has 23 entrys.

Regards Gert

[john korterman]

Hi,
what does your queuedefs look like? Perhaps the limit for at jobs is less than 5 and the error message concerns this?
Sounds like a stupid question, but I have to ask as the standard limit is 4.

regards,
John K.

[Gert Svedvall]

These are the settings:
a.5j1n
b.2j2n90w

Due to application reasons the at-jobs are
running allday and are the only one scheduled that way, everything else is run by cron.

[john korterman]

Hi again Gert,
you can at least have 5 at jobs running simultaneously, but is there not the slightest possibility that an at job may be started before another has finsished, thus creating more than 5 simultanous at jobs?

regards,
John K.

[Gert Svedvall]

These at-jobs are workarounds due to a shaky network and acts the same way as "respawn" in
/etc/inittab (there are reasons why we're not
using respawn)

[john korterman]

Hi again,
it sounds then to me as if there is no check on whether an at job is already running before a new one is started up. Without knowing the detailed circumstances I have only two suggestions:
a) insert a check in each at job which prevents more than a single instance of each job running.
b) increase the number of simultaneous jobs from 5 to e.g. 15. Not very nice, but if it helps, it points to the core of the problem.

Maybe the other forum members have suggestions when they wake up.

regards,
John K.

[Gert Svedvall]

Hi John.
It just came to my thinking that one of the progammers mentioned something about "putting a few job in the bucket" just to prevent the session from going down, I'll check with him and let you know.

[Gert Svedvall]

I found the "guilty" one, it was a "dirty workaround" but thanks anyway for helping me sorting out how cronqueue works

//Gert