queued cron process

[SILO Storagetek]

I reached the maximum number of queued cron process (cron.log: MAXRUN (100) procs reached).

As workaround I decided to restart the cron daemon (kill + /sbin/init.d/cron start) loosing the queued procs.
Now the scheduling run perfectly.

I've 2 questions:
- is it possible to exceed the limit of 100 simultaneus procs modifing some parameters? (i think no).
- is it possibile to know what are the queued procs ?

TIA for the response

[Robert-Jan Goossens]

Hi,

Max jobs is 100

http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063199330

Kind regards,

Robert-Jan.

[Steve Steel]

Hi


look at

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x4034eea29889d611abdb0090277a778c,00.html

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xec9fee3e323bd5118fef0090279cd0f9,00.html

Regards

Steve Steel

Quote of the moment
-------------------
"We are drowning in information but starved for knowledge."
-- John Naisbitt

[T G Manikandan]

If you are running hpux 11.0
you have to install this patch to resolve

PHCO_27141


Thanks

[T G Manikandan]

check this link

http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf6dc0bce6f33d6118fff0090279cd0f9,00.html

[Pete Randall]

This applies more to at and batch jobs than cron, but, since they all contribute to the MAXRUN count:

If you have PHCO_24702 installed, you need to install PHCO_27141. "PHCO_24702 introduced behavior whereby cron(1M) may no
longer
execute at(1) jobs. When one of the environment variables
LC_ALL, LC_CTYPE or LANG is set when an at(1) job is
scheduled, at(1) jobs may not complete and may leave the
executing shell in a hung state. "


Pete

[SILO Storagetek]

I've the 11i 1.5.

I'v had the confirmation that the limit is 100, is there a way to show the cron queue (name of the process) ?

Thanks again

[John Palmer · Accepted solution]

Processes started by cron and still running can be identified by the fact that cron is their parent.

You could try the following...
1. Identify cron's PID
UNIX95= ps -C cron -o pid,comm
2. Display possible child processes...
ps -ef | grep
and check the PPID.

Or use ps's -H flag to display the process hierarchy...
UNIX95= ps -eH | more
and search for cron.

UNIX95= ps -efH gives more information.

Regards,
John

[Chris Vail]

If you have more than 100 jobs in cron, you really need to look at a 3rd party application to run your batch jobs. We use Tivoli Workload Scheduler, which is expensive, clunky and badly written. But it does a lot of stuff that cron can't. The best part is that you can offload the maintenence of your batch jobs to your endusers.