<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: queued cron process in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858342#M95474</link>
    <description>I've the 11i 1.5.&lt;BR /&gt;&lt;BR /&gt;I'v had the confirmation that the limit is 100, is there a way to show the cron queue (name of the process) ?&lt;BR /&gt;&lt;BR /&gt;Thanks again</description>
    <pubDate>Thu, 05 Dec 2002 11:49:42 GMT</pubDate>
    <dc:creator>SILO Storagetek</dc:creator>
    <dc:date>2002-12-05T11:49:42Z</dc:date>
    <item>
      <title>queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858336#M95468</link>
      <description>I reached the maximum number of queued cron process (cron.log: MAXRUN (100) procs reached).&lt;BR /&gt;&lt;BR /&gt;As workaround I decided to restart the cron daemon (kill + /sbin/init.d/cron start) loosing the queued procs.&lt;BR /&gt;Now the scheduling run perfectly.&lt;BR /&gt;&lt;BR /&gt;I've 2 questions:&lt;BR /&gt;- is it possible to exceed the limit of 100 simultaneus procs modifing some parameters? (i think no).&lt;BR /&gt;- is it possibile to know what are the queued procs ?&lt;BR /&gt;&lt;BR /&gt;TIA for the response&lt;BR /&gt;&lt;BR /&gt;  &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Dec 2002 10:43:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858336#M95468</guid>
      <dc:creator>SILO Storagetek</dc:creator>
      <dc:date>2002-12-05T10:43:13Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858337#M95469</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Max jobs is 100&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000063199330" target="_blank"&gt;http://www5.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&amp;amp;docId=200000063199330&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Robert-Jan.&lt;BR /&gt;</description>
      <pubDate>Thu, 05 Dec 2002 10:50:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858337#M95469</guid>
      <dc:creator>Robert-Jan Goossens</dc:creator>
      <dc:date>2002-12-05T10:50:10Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858338#M95470</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;look at&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x4034eea29889d611abdb0090277a778c,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0x4034eea29889d611abdb0090277a778c,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xec9fee3e323bd5118fef0090279cd0f9,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xec9fee3e323bd5118fef0090279cd0f9,00.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;                       Regards&lt;BR /&gt;&lt;BR /&gt;                       Steve Steel&lt;BR /&gt;&lt;BR /&gt;Quote of the moment&lt;BR /&gt;-------------------&lt;BR /&gt;"We are drowning in information but starved for knowledge."&lt;BR /&gt;-- John Naisbitt</description>
      <pubDate>Thu, 05 Dec 2002 10:51:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858338#M95470</guid>
      <dc:creator>Steve Steel</dc:creator>
      <dc:date>2002-12-05T10:51:13Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858339#M95471</link>
      <description>If you are running hpux 11.0&lt;BR /&gt;you have to install this patch to resolve&lt;BR /&gt;&lt;BR /&gt;PHCO_27141 &lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Thu, 05 Dec 2002 10:53:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858339#M95471</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-12-05T10:53:44Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858340#M95472</link>
      <description>check this link&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf6dc0bce6f33d6118fff0090279cd0f9,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xf6dc0bce6f33d6118fff0090279cd0f9,00.html&lt;/A&gt;</description>
      <pubDate>Thu, 05 Dec 2002 11:08:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858340#M95472</guid>
      <dc:creator>T G Manikandan</dc:creator>
      <dc:date>2002-12-05T11:08:46Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858341#M95473</link>
      <description>This applies more to at and batch jobs than cron, but, since they all contribute to the MAXRUN count:&lt;BR /&gt;&lt;BR /&gt;If you have PHCO_24702 installed, you need to install PHCO_27141.  "PHCO_24702 introduced behavior whereby cron(1M) may no&lt;BR /&gt;                                                  longer &lt;BR /&gt;                                                  execute at(1) jobs. When one of the environment variables &lt;BR /&gt;                                                  LC_ALL, LC_CTYPE or LANG is set when an at(1) job is &lt;BR /&gt;                                                  scheduled, at(1) jobs may not complete and may leave the &lt;BR /&gt;                                                  executing shell in a hung state. "&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Pete</description>
      <pubDate>Thu, 05 Dec 2002 11:16:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858341#M95473</guid>
      <dc:creator>Pete Randall</dc:creator>
      <dc:date>2002-12-05T11:16:59Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858342#M95474</link>
      <description>I've the 11i 1.5.&lt;BR /&gt;&lt;BR /&gt;I'v had the confirmation that the limit is 100, is there a way to show the cron queue (name of the process) ?&lt;BR /&gt;&lt;BR /&gt;Thanks again</description>
      <pubDate>Thu, 05 Dec 2002 11:49:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858342#M95474</guid>
      <dc:creator>SILO Storagetek</dc:creator>
      <dc:date>2002-12-05T11:49:42Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858343#M95475</link>
      <description>Processes started by cron and still running can be identified by the fact that cron is their parent.&lt;BR /&gt;&lt;BR /&gt;You could try the following...&lt;BR /&gt;1. Identify cron's PID&lt;BR /&gt;UNIX95= ps -C cron -o pid,comm&lt;BR /&gt;2. Display possible child processes...&lt;BR /&gt;ps -ef | grep &lt;CRON&gt;&lt;BR /&gt;and check the PPID.&lt;BR /&gt;&lt;BR /&gt;Or use ps's -H flag to display the process hierarchy...&lt;BR /&gt;UNIX95= ps -eH | more&lt;BR /&gt;and search for cron.&lt;BR /&gt;&lt;BR /&gt;UNIX95= ps -efH gives more information.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;John&lt;/CRON&gt;</description>
      <pubDate>Thu, 05 Dec 2002 12:48:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858343#M95475</guid>
      <dc:creator>John Palmer</dc:creator>
      <dc:date>2002-12-05T12:48:47Z</dc:date>
    </item>
    <item>
      <title>Re: queued cron process</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858344#M95476</link>
      <description>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.</description>
      <pubDate>Thu, 05 Dec 2002 16:49:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/queued-cron-process/m-p/2858344#M95476</guid>
      <dc:creator>Chris Vail</dc:creator>
      <dc:date>2002-12-05T16:49:13Z</dc:date>
    </item>
  </channel>
</rss>

