<?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: /usr/bin/lp: request ids exhausted for printer in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444473#M357850</link>
    <description>oops, too fast of a finger I have.. I also meant to say, did you check the permissions and ownership of the /var/spool/lp/seqfile ? it usually have owner and group both set to lp and permission is 644.&lt;BR /&gt;</description>
    <pubDate>Mon, 22 Jun 2009 14:33:34 GMT</pubDate>
    <dc:creator>Mel Burslan</dc:creator>
    <dc:date>2009-06-22T14:33:34Z</dc:date>
    <item>
      <title>/usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444471#M357848</link>
      <description>Does anyone have an idea on how to resolve the following error related to printer request id allocation?&lt;BR /&gt;/usr/bin/lp: request ids exhausted for printer:cabs_label1&lt;BR /&gt;The current workaround, I’ve resorted to is running the following command every 6hrs through cron.&lt;BR /&gt;cat /dev/null &amp;gt; /var/spool/lp/seqfile&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jun 2009 14:21:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444471#M357848</guid>
      <dc:creator>Shibu George P</dc:creator>
      <dc:date>2009-06-22T14:21:03Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444472#M357849</link>
      <description>What you are doing sounds like band-aid solution to a huge wound. Do you have any idea why the request id's getting depleted so often. Is the printer queue stuck with a lot of jobs pending it it ?</description>
      <pubDate>Mon, 22 Jun 2009 14:27:24 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444472#M357849</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2009-06-22T14:27:24Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444473#M357850</link>
      <description>oops, too fast of a finger I have.. I also meant to say, did you check the permissions and ownership of the /var/spool/lp/seqfile ? it usually have owner and group both set to lp and permission is 644.&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jun 2009 14:33:34 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444473#M357850</guid>
      <dc:creator>Mel Burslan</dc:creator>
      <dc:date>2009-06-22T14:33:34Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444474#M357851</link>
      <description>The current permission is&lt;BR /&gt;-rwxr-x---   1 lp         lp               4 Jun 22 16:37 /var/spool/lp/seqfile&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Jun 2009 14:42:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444474#M357851</guid>
      <dc:creator>Shibu George P</dc:creator>
      <dc:date>2009-06-22T14:42:00Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444475#M357852</link>
      <description>I changed the permission to 754.  Still the problem persists</description>
      <pubDate>Mon, 22 Jun 2009 14:53:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444475#M357852</guid>
      <dc:creator>Shibu George P</dc:creator>
      <dc:date>2009-06-22T14:53:17Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444476#M357853</link>
      <description>&amp;gt;The current permission is: -rwxr-x--- 1 lp lp seqfile&lt;BR /&gt;&lt;BR /&gt;Data files shouldn't be executable.  Use "chmod a-x seqfile".</description>
      <pubDate>Mon, 22 Jun 2009 19:55:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444476#M357853</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2009-06-22T19:55:44Z</dc:date>
    </item>
    <item>
      <title>Re: /usr/bin/lp: request ids exhausted for printer</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444477#M357854</link>
      <description>Perhaps some has been playing around with permissions and ownerships. Run swverify:&lt;BR /&gt; &lt;BR /&gt;swverify PrinterMgmt&lt;BR /&gt; &lt;BR /&gt;Other than the man pages, correct the permission and ownership errors.</description>
      <pubDate>Tue, 23 Jun 2009 01:44:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/usr-bin-lp-request-ids-exhausted-for-printer/m-p/4444477#M357854</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2009-06-23T01:44:49Z</dc:date>
    </item>
  </channel>
</rss>

