<?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: lpsched in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502840#M216879</link>
    <description>Did you run glance or top to see which lp process was taking up the CPU? Or if it was more than one process. Could be a application problem constantly sending print jobs. What does 'lpstat -t' show?</description>
    <pubDate>Fri, 11 Mar 2005 16:35:07 GMT</pubDate>
    <dc:creator>Robert Salter</dc:creator>
    <dc:date>2005-03-11T16:35:07Z</dc:date>
    <item>
      <title>lpsched</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502837#M216876</link>
      <description>Hi All&lt;BR /&gt;Does anyone know why lpsched would hogg my system. 96% cpu usage.&lt;BR /&gt;&lt;BR /&gt;I am running a Service Gaurd cluster on a 2 node K570 servers running 10.20.&lt;BR /&gt;When this happens, the system is dead slow. I have to kill all the lp processes and try to startup lpsched again.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance&lt;BR /&gt;Shaamil</description>
      <pubDate>Fri, 11 Mar 2005 08:58:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502837#M216876</guid>
      <dc:creator>Shaamil</dc:creator>
      <dc:date>2005-03-11T08:58:20Z</dc:date>
    </item>
    <item>
      <title>Re: lpsched</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502838#M216877</link>
      <description>Most of the time this is becasue of wrong printer name , it has  to be the same as the name in /etc/hosts or in DNS associated with the ip address of your printer.&lt;BR /&gt;This could happen if an incorrect peripheral name for your printer,you must remove and readd the printer to the spooler using the correct peripheral name .&lt;BR /&gt;Goodluck,&lt;BR /&gt;-USA..</description>
      <pubDate>Fri, 11 Mar 2005 09:04:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502838#M216877</guid>
      <dc:creator>Uday_S_Ankolekar</dc:creator>
      <dc:date>2005-03-11T09:04:11Z</dc:date>
    </item>
    <item>
      <title>Re: lpsched</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502839#M216878</link>
      <description>I will check with my application users, which printer it is that they are using. We have about 20 printers on the system.&lt;BR /&gt;Thanks,&lt;BR /&gt;Shaamil</description>
      <pubDate>Fri, 11 Mar 2005 09:09:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502839#M216878</guid>
      <dc:creator>Shaamil</dc:creator>
      <dc:date>2005-03-11T09:09:22Z</dc:date>
    </item>
    <item>
      <title>Re: lpsched</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502840#M216879</link>
      <description>Did you run glance or top to see which lp process was taking up the CPU? Or if it was more than one process. Could be a application problem constantly sending print jobs. What does 'lpstat -t' show?</description>
      <pubDate>Fri, 11 Mar 2005 16:35:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502840#M216879</guid>
      <dc:creator>Robert Salter</dc:creator>
      <dc:date>2005-03-11T16:35:07Z</dc:date>
    </item>
    <item>
      <title>Re: lpsched</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502841#M216880</link>
      <description>The lpsched consuming all the CPU time will be the parent of a shell that is running the shell script.The shell script is the name of the local printer. To see the hierarchy of processes, use this:&lt;BR /&gt; &lt;BR /&gt;UNIX95= ps -ulp -H -o pid,ppid,time,args&lt;BR /&gt; &lt;BR /&gt;The highest level lpsched has a parent ID (PPID) of 1 and all other lpscheds will have this first lpsched as their parent. Look for the lpsched that is taking all the CPU time, then look at it's child process which will be the shell running the printer script. That printer is the problem. Fixing it depends on how it is connected, local via copper cable, local via HP JetDirect networking or remote to a non-HP printer or remote print server.</description>
      <pubDate>Fri, 11 Mar 2005 20:08:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502841#M216880</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2005-03-11T20:08:37Z</dc:date>
    </item>
    <item>
      <title>Re: lpsched</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502842#M216881</link>
      <description>Thanks for the response guys. My printers are all idle for the weekend, but I will let U know how it goes next week. I am away next week as well.</description>
      <pubDate>Sat, 12 Mar 2005 03:10:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/lpsched/m-p/3502842#M216881</guid>
      <dc:creator>Shaamil</dc:creator>
      <dc:date>2005-03-12T03:10:19Z</dc:date>
    </item>
  </channel>
</rss>

