<?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: Spooler Problems! in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573107#M857775</link>
    <description>The command cancel -e cancels all the print jobs from all printers.&lt;BR /&gt;&lt;BR /&gt;Vince</description>
    <pubDate>Fri, 31 Aug 2001 06:21:30 GMT</pubDate>
    <dc:creator>Vincent Farrugia</dc:creator>
    <dc:date>2001-08-31T06:21:30Z</dc:date>
    <item>
      <title>Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573102#M857770</link>
      <description>I am having a few problems restarting the scheduler. It says it's started, but it really isn't? Any ideas?&lt;BR /&gt;&lt;BR /&gt;Thanks&lt;BR /&gt;&lt;BR /&gt;# /usr/sbin/lpshut                        &lt;BR /&gt;usr/sbin/lpshut: scheduler not running   &lt;BR /&gt; #/usr/sbin/lpsched                       &lt;BR /&gt;cheduler is running                      &lt;BR /&gt; #lpstat -r                               &lt;BR /&gt;cheduler is not running                  &lt;BR /&gt;</description>
      <pubDate>Thu, 30 Aug 2001 18:13:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573102#M857770</guid>
      <dc:creator>Mike_21</dc:creator>
      <dc:date>2001-08-30T18:13:06Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573103#M857771</link>
      <description>Typically this happens when the lockfiles are not removed or more than 1 lpsched process is running.&lt;BR /&gt;&lt;BR /&gt;1) lpshut&lt;BR /&gt;2) do a ps -e | grep lpsched. If another lpsched is running kill it using the process id obtained from ps.&lt;BR /&gt;3) cd /var/spool/lp&lt;BR /&gt;   if the files FIFO or SCHEDLOCK are found, remove them&lt;BR /&gt;4) lpsched&lt;BR /&gt;&lt;BR /&gt;That should fix you.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Aug 2001 18:23:33 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573103#M857771</guid>
      <dc:creator>A. Clay Stephenson</dc:creator>
      <dc:date>2001-08-30T18:23:33Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573104#M857772</link>
      <description>If you want to get a better idea of what is going on, try again but use the command&lt;BR /&gt;lpsched -v&lt;BR /&gt;...this will write a verbose record to &lt;BR /&gt;/var/adm/lp/log .&lt;BR /&gt;Probably don't want to leave it that way, but should help you get a better picture of what is going on.&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Aug 2001 18:24:37 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573104#M857772</guid>
      <dc:creator>Jay Newman</dc:creator>
      <dc:date>2001-08-30T18:24:37Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573105#M857773</link>
      <description>After shutdown the spooler, check&lt;BR /&gt;/var/spool/lp&lt;BR /&gt;If there are FIFO and SCHEDLOCK, remove them and try to start your spooler again.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Thu, 30 Aug 2001 18:24:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573105#M857773</guid>
      <dc:creator>Victor_5</dc:creator>
      <dc:date>2001-08-30T18:24:58Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573106#M857774</link>
      <description>FIFO and SCHEDLOCK don't exist.. Is there a command to cancel all jobs pending in the print q?&lt;BR /&gt;&lt;BR /&gt;cancal maybe?</description>
      <pubDate>Thu, 30 Aug 2001 18:33:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573106#M857774</guid>
      <dc:creator>Mike_21</dc:creator>
      <dc:date>2001-08-30T18:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573107#M857775</link>
      <description>The command cancel -e cancels all the print jobs from all printers.&lt;BR /&gt;&lt;BR /&gt;Vince</description>
      <pubDate>Fri, 31 Aug 2001 06:21:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573107#M857775</guid>
      <dc:creator>Vincent Farrugia</dc:creator>
      <dc:date>2001-08-31T06:21:30Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573108#M857776</link>
      <description>Hi,&lt;BR /&gt;First cancel all the print jobs with cancel -e&lt;BR /&gt;then try /sbin/init.d/lp stop and /sbin/init.d/lp start.&lt;BR /&gt;&lt;BR /&gt;best of luck&lt;BR /&gt;Animesh</description>
      <pubDate>Fri, 31 Aug 2001 08:24:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573108#M857776</guid>
      <dc:creator>Animesh Chakraborty</dc:creator>
      <dc:date>2001-08-31T08:24:20Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573109#M857777</link>
      <description>The problem was that someone tried to remove a print queue the wrong way. The log file was looking for a directory  in /var/spool/lp/request that did not exist. I simply added the directyory back and the spooler came back up.</description>
      <pubDate>Fri, 31 Aug 2001 16:42:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573109#M857777</guid>
      <dc:creator>Mike_21</dc:creator>
      <dc:date>2001-08-31T16:42:44Z</dc:date>
    </item>
    <item>
      <title>Re: Spooler Problems!</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573110#M857778</link>
      <description>What about this.&lt;BR /&gt;&lt;BR /&gt;# /usr/lib/lpshut&lt;BR /&gt;# cd /usr/spool/lp&lt;BR /&gt;# cat /dev/null &amp;gt; pstatus&lt;BR /&gt;# cat /dev/null &amp;gt; qstatus&lt;BR /&gt;# cat /dev/null &amp;gt; output&lt;BR /&gt;# lpsched&lt;BR /&gt;&lt;BR /&gt;Best of luck.</description>
      <pubDate>Mon, 03 Sep 2001 00:46:28 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/spooler-problems/m-p/2573110#M857778</guid>
      <dc:creator>Kiyoung</dc:creator>
      <dc:date>2001-09-03T00:46:28Z</dc:date>
    </item>
  </channel>
</rss>

