- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- TRU 64 Printing
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2003 03:15 AM
тАО06-18-2003 03:15 AM
We currently have 13 printers that are printing remotely from this server. The problem is that whenever any of the 13 printers is unplugged for any reason this stops the print jobs to the other servers. When this happens I have to restart the spooler to get the jobs to print.
Is there any way to get around this issue? We really only need our two main printers running all the time. Is using a different port for those two printers an option?
Thanks
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2003 04:26 AM
тАО06-18-2003 04:26 AM
Re: TRU 64 Printing
lpc disable queuename
lpc down queuename
Once I've brought the printer back online, I then bring up and re-enable the queue:
lpc up queuename
lpc enable queuename
HTH,
Mike-
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-18-2003 10:02 PM
тАО06-18-2003 10:02 PM
Re: TRU 64 Printing
Which patchkit is installed?
Are all the printers connected to the same printserver?
What does /var/adm/syslog.dated/current/lpr.log say about the time one of the printers is down?
Could you please post one of the printcap entries?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2003 07:48 AM
тАО06-26-2003 07:48 AM
Re: TRU 64 Printing
To answer your questions:
We are running 5.1A.
I am unsure what patchkit we have. I try the dupatch command and it says command not found and I'm not sure exactly how to find this info.
We have different print servers for the servers.(servers are at various locations)
Here is the output from lpr.log. Many entries like this one. This was caused by somebody unplugging the printer.
Jun 13 21:18:13 hostname lpd[74952]: INFO -- openpr: getport() failed, have alre
ady waited 18175 seconds for 192.168.107.87 to come up
Here is an entry from the printcap
hp-office|lp1: :lf=/usr/adm/hp-office-err: :lp=: :rm=192.168.0.33: :rp=TEXT: :sd=/usr/spool/hp-office: :sh:
Thanks,
Dave
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2003 10:49 PM
тАО06-26-2003 10:49 PM
Re: TRU 64 Printing
In previous versions there was the same problem with printing, failing if one printer was stalled or waiting for paper. Be sure you have installed the latest patchkit to fix this issue.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2003 11:51 PM
тАО06-26-2003 11:51 PM
SolutionThe dupatch command comes with the patchkit.
So, if you have the "command not found" error, I believe that no patchkit is installed.
Or, you do not have /usr/sbin in your PATH variable.
If you want to know the installed patchkits, you can use following command.
# /usr/sbin/dupatch -track -type kit
Anyway, in attachment you have a readme of the latest patchkit. It contains also it's network location.
Joris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-26-2003 11:59 PM
тАО06-26-2003 11:59 PM
Re: TRU 64 Printing
The links in the attachment are not yet OK.
You need the t64v51ab21as0004-20030206.* files in
ftp://ftp.support.compaq.com/public/Digital_UNIX/v5.1a
Joris
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО06-27-2003 04:38 AM
тАО06-27-2003 04:38 AM