<?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: printer job re-send problem in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109365#M312995</link>
    <description>&lt;BR /&gt;if you stop/start te print deamons it will alsow resend the jop.&lt;BR /&gt;&lt;BR /&gt;be aware that if you have manny jops (&amp;gt;100)the stop start can take over more than a our. so if you are plannng to stop start every our make sure that the queue is not filled to match.&lt;BR /&gt;&lt;BR /&gt;I think you can set the resend alsow whit in lpsched, if you turn it in it will resent every 2 ours. (at this time I can not find how)</description>
    <pubDate>Thu, 29 Nov 2007 05:22:53 GMT</pubDate>
    <dc:creator>F Verschuren</dc:creator>
    <dc:date>2007-11-29T05:22:53Z</dc:date>
    <item>
      <title>printer job re-send problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109364#M312994</link>
      <description>Hi expert,&lt;BR /&gt;   I've a query about lpsched. The network is not stable. Sometimes it would dis-connection, and networking will live after 10 seconcds.&lt;BR /&gt;&lt;BR /&gt;   in the such situration, while I use "lp" to print out job, the job would queued in the network down. But the print job would not re-send while networking was back.&lt;BR /&gt;&lt;BR /&gt;   My question is, is lpsched would se-send job if the job queued? how to do it? Thanks in advanced.</description>
      <pubDate>Thu, 29 Nov 2007 01:03:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109364#M312994</guid>
      <dc:creator>j773303</dc:creator>
      <dc:date>2007-11-29T01:03:10Z</dc:date>
    </item>
    <item>
      <title>Re: printer job re-send problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109365#M312995</link>
      <description>&lt;BR /&gt;if you stop/start te print deamons it will alsow resend the jop.&lt;BR /&gt;&lt;BR /&gt;be aware that if you have manny jops (&amp;gt;100)the stop start can take over more than a our. so if you are plannng to stop start every our make sure that the queue is not filled to match.&lt;BR /&gt;&lt;BR /&gt;I think you can set the resend alsow whit in lpsched, if you turn it in it will resent every 2 ours. (at this time I can not find how)</description>
      <pubDate>Thu, 29 Nov 2007 05:22:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109365#M312995</guid>
      <dc:creator>F Verschuren</dc:creator>
      <dc:date>2007-11-29T05:22:53Z</dc:date>
    </item>
    <item>
      <title>Re: printer job re-send problem</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109366#M312996</link>
      <description>Since the network is so bad, you'll have to write a script to monitor the network status, then restart the lp spooler. You can just use lpshut and lpsched to restart the spooler. However, since there are different ways to send print jobs, the spooler may not be successful in shutting down all the pending jobs, so your script will have to find all lp jobs and issue various kill signals with waits in order to terminate everything.</description>
      <pubDate>Thu, 29 Nov 2007 07:11:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/printer-job-re-send-problem/m-p/4109366#M312996</guid>
      <dc:creator>Bill Hassell</dc:creator>
      <dc:date>2007-11-29T07:11:07Z</dc:date>
    </item>
  </channel>
</rss>

