06-10-2009
Please post the command you typed and the output.
Also please state you Operating System in case there is a simple dodge by counting spool data files in the spool directory.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I have a printer in another state that is setup as follows:
lj8100 printer connected to their printserver (a w2k box);
users connect to a unix app on our Sun server via Exceed (we are two states away via WAN);
users submit print jobs through an established print queue through the unix app to... (0 Replies)
Discussion started by: antalexi
0 Replies
2. SCO
I have implemented Laser printers using USB printer servers connected to a SCO server. Sometimes print jobs get stuck on the queue and I havent found a way of getting the printer back to work without canceling the jobs and rebooting the system.
Why jobs get stuck?
How do I get this solved... (9 Replies)
Discussion started by: iNetForce
9 Replies
3. UNIX for Dummies Questions & Answers
I am trying to create a printer queue, on a SunOS 5.7 system, that outputs a pdf file. There is an application running on the system that has a print button, which sends print files to the default printer. If I disable the printer, I am able to manually capture the files in /var/spool/lp/tmp and... (1 Reply)
Discussion started by: Sean_69
1 Replies
4. Solaris
I am trying to create a printer queue, on a SunOS 5.7 system, that outputs a pdf file. There is an application running on the system that has a print button, which sends print files to the default printer. If I disable the printer, I am able to manually capture the files in /var/spool/lp/tmp and... (2 Replies)
Discussion started by: Sean_69
2 Replies
5. HP-UX
Hello,
I have a print queue that the jobs are getting stuck in. I've disabled and enabled the queue, lpshut and lpsched the print spooler, and killed a suspected corrupt job. But new requests still get stuck. I can ping the printer by DNS with no problem. What else can I look for? I'm a little... (3 Replies)
Discussion started by: mizzleman
3 Replies
6. Shell Programming and Scripting
Hi,
i m having problem to get number of jobs waiting using lpstat.my printer is out of paper and 10jobs are in queue but i run lpstat -pqname it didnt show any thing.any one have idea whats wrong here. thanks
sagii (2 Replies)
Discussion started by: sagii
2 Replies
7. AIX
Hi
I had setup a print queue named test in the AIX server. When I try to print 96 char per line.. it prints only 80 and the rest is skipped to the next line.
however there are 16 spaces left as blank in the first line
any help is appriciated (0 Replies)
Discussion started by: antointoronto
0 Replies
8. UNIX for Advanced & Expert Users
Hello,
Sometimes i need to clear all the jobs of a print queue and it is really annoying to cancel one by one.
Is there a way to cancel all print jobs for a specific print queue with a single command instead of cancelling them one by one?
My AIX system is 5.3
Thank you for your attention (2 Replies)
Discussion started by: omonoiatis9
2 Replies
9. 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
10. AIX
Hi, have an aix system with something I've never seen happening. All printers are not printing. I see jobs Queued and printer status as READY but jobs just keep getting queued and nothing's printing. Seems to be a system wide problem since it's affecting all printers. Help... (2 Replies)
Discussion started by: flash88
2 Replies
LEARN ABOUT XFREE86
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)