Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations gkittelson on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Print Job Manager problem

Status
Not open for further replies.

blabelle

Technical User
May 2, 2002
40
US
The previous request for help fixed the cancel problem I had
(I think)but when I go into Print Job Manager the "Refreshing print job list..." just keeps running and doesn't give me the current print jobs. Which makes me think that there are still some bad jobs trying to run. How can I check and fix this.
Thanks.
SCO openserver 5.6
 
You might want to check pending jobs by running the "lpstat -o" command instead of the menu-based process.
Also, if you have any LPR-based remote printers, they often don't respond to status requests in a timely manner, and SCO doesn't like to give up trying. Thus, the "hang" situation.

 
When I do the lpstat -o it also hangs and slowly shows all the printers with nothing in their queue
 
This is directly off SCO's support page:

You need to decrease the value of the TCP/IP parameter 'tcp_initial_timeout', defined as :
Sets the TCP/IP retransmit time for an initial SYN segment. The default value is 180 seconds as defined by RFC 1122. The minimum and maximum configurable values are 1 and 7200 seconds.

Setting this to a lower value (say 10 seconds) will cause the timeout to occur in a reasonable time, and will give the status of the other printers. To change this parameter, execute the following command (a re-boot is not required) :


inconfig tcp_initial_timeout 10

You should now get output from lpstat similar to the
following :

# lpstat -o
adminpr1:
192.168.245.112: Connection timed out
connection to 192.168.245.231 is down
salespr1:
JetDirect lpd: no jobs queued on this port


See Also
inconfig(ADMN)

See if this applies to your situation. Hope it helps.
 
It turns out that the printers that are hanging are remote printers that are configured on a WinXP machine with RPM. Is there any way to cause these printers show in lpstat faster? They all timeout with 10sec timeout. I will research the RPM support for this problem. But if you have seen this befor and have a fix I would appreciate it.
Thanks
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top