06-06-2011
Quote:
There is no error generated that I can find. When I submit a print job the queue simply goes down. It seems like I had this working at one time but my notes are a bit sketchy. As for using a 14 year old OS....yes we really do and yes it is a production system. Not my choosing but the pay is the same.
Regarding the OS version: i suppose you can't upgrade that much because your hardware might not be supported after 5.1 (if you have a really old R/6000 system, that is). Still you might consider upgrading to 4.3.3 ML11(12? 10? can't remember which was the last one), which was a lot more reliable than 4.2.1 and most likely your software will run with that too.
Regarding your printer problem: have you had a look at "/var/spool/qdaemon" and the files there? This is where the printing subsystem stores its files.
I hope this helps.
bakunin
10 More Discussions You Might Find Interesting
1. AIX
Hi all,
I have an interesting problem. Using remote queues to print using jetdirect printers I am unable to get a printer to print multiple copies of a print job.
command being used:
lpr -P -#3 ./test
(one copy prints)
Also tried:
enq -P -C3 ./test
(same results)
Any ideas?
... (6 Replies)
Discussion started by: Luck
6 Replies
2. Linux
Hello,
I am using version:
cups-config --version - 1.2.4
However, when i use the -o land or -o landscape command it doesn't print in Landscape.
I have the same problem on another server. (Both running CENTOS).
Does landscape printing work in CUPS? Is there a fix?
Thanks in an... (0 Replies)
Discussion started by: stuaz
0 Replies
3. AIX
Hello,
I am trying to setup remote printing from a Linux machine (Red Hat 5.3) to an AIX machine (AIX 5.3). Remote printing for "normal" print jobs is working out OK, but I'm having trouble with some AIX printers that have a user defined backend.
I turned on logging for lpd on the AIX... (0 Replies)
Discussion started by: sbaker
0 Replies
4. Red Hat
Hello,
I also posted this on the AIX forum in hopes of getting help.
I am trying to setup remote printing from a Linux machine (Red Hat 5.3) to an AIX machine (AIX 5.3). Remote printing for "normal" print jobs is working out OK, but I'm having trouble with some AIX printers that have a user... (0 Replies)
Discussion started by: sbaker
0 Replies
5. SCO
Hi, i'm running Openserver 5.0.7 as a CUPS client for a Linux server. The root user can issue a "lpstat -t" to see the printers and can submit jobs without issues.
The problem presents when I try to work as a regular user. If I issue an "lpstat -t" all I get after a few seconds is "lpstat:... (1 Reply)
Discussion started by: cyruspy
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
We have a Unix 3.2v5.0.5.
I installed a printer via scoadmin, HP network printer manager with network peripheral name (hostname and ipadres are in /etc/hosts).
This is the configuration file :
Code:
root@sco1 # cat configurationBanner: on:AlwaysContent types: simpleDevice:... (0 Replies)
Discussion started by: haezeban
0 Replies
7. UNIX for Advanced & Expert Users
Hi Guys,
I've inherited a mess of an infrastructure in my new job, there hasn't been a sys admin in post for about a year, so things are falling apart. The first thing to break after I started was the printer server. I have it working again, and people can print, however it's very slow, slower... (0 Replies)
Discussion started by: rudigarude
0 Replies
8. Red Hat
Hi All,
Having searched for a solution to this issue i found no suggestions which help my particular problem.
I am getting the following error message on 1 of the 3 printers i have configured:
recoverable: Network host 'xxx.xxx.xxx.xxx' is busy; will retry in 30 seconds
All 3 printers are... (0 Replies)
Discussion started by: Tommyk
0 Replies
9. UNIX for Advanced & Expert Users
Hello Experts,
I have been facing an issue with printing through cups configured on Linux server.
All was going on well but all of a sudden the printers started giving an error message, "Unsupported format application/postscript!" and we cant get any prints of any printer.
Need your help as... (2 Replies)
Discussion started by: Rockyc3400
2 Replies
10. UNIX for Advanced & Expert Users
Hi everyone,
Our office has a lot of printers (label & laser), and sometimes it gets quite hard to configure a new printer in CUPS as most printer manufactures does not provide drivers/ppd for CUPS/LINUX/UNIX.
So we are trying to move to a Windows Print Server and run a Proof of concept. We... (2 Replies)
Discussion started by: Syed Hussaini
2 Replies
lpq(1) General Commands Manual lpq(1)
Name
lpq - spool queue examination program
Syntax
lpq [ options ] [ job #... ] [ user... ]
Description
The command examines the spooling area used by for printing files on the printer, and reports the status of jobs. The command invoked
without any arguments reports on any jobs currently in the default queue.
When jobs are being printed, reports the queue as being ``active''. For each job submitted, reports the user's name, current rank in the
queue, the names of files comprising the job, the job identifier and the total size in bytes. The job identifier is a number which may be
supplied to to remove a specific job.
Job ordering is determined by the FIFO (First In, First Out) algorithm used to scan the spooling directory. When the queue is empty,
reports that there are ``no entries''.
File names may be unavailable for some jobs, for example, if the command is used without specifying a file name, or if is used in a pipe
line. If file names are unavailable, the file name reported by is ``standard input''.
Arguments
job #... Causes to report on only the job number(s) specified.
user... Causes to report on only the jobs for the specified user(s).
Options
+n Scan and display the spool queue until the queue is empty. The queue is scanned every n seconds, if no argument is specified the
queue is scanned every 30 seconds.
-l Display the status of each job on more than one line if necessary. If this option is not used, the status of each job is displayed on
one line.
-Pprinter
Report the status of the spool queue for the printer specified. If this option is not used, the spool queue displayed is the one
defined by the PRINTER environment variable. If a queue is not defined by the PRINTER environment variable, the spool queue displayed
is for the printer named ``lp'' in the file.
Restrictions
The displayed status of the spool queue may not always be the current status. This is because jobs may be completed after the queue has
been examined, but before the status has been displayed.
Error Messages
Two of the most common error messages from are:
Warning: no daemon present (R)
A daemon is not available for the specified printer. Refer to the command to find out how to restart the printer daemon.
unknown printer (R)
The printer specified as an argument to the -P option, doesn't have an entry in the file.
Files
For manipulating the screen for repeated display
To determine printer characteristics
The spooling directory, as determined from printcap
Control files specifying jobs
The lock file to obtain the currently active job
See Also
lpr(1), lprm(1), lpc(8), lpd(8)
lpq(1)