Sponsored Content
Full Discussion: print q jobs
Top Forums Shell Programming and Scripting print q jobs Post 302328942 by sagii on Thursday 25th of June 2009 01:53:36 PM
Old 06-25-2009
thanks for reply. actually i need to consider READY state too not only DOWN or QUEUE. in case printer is in ready state but number of jobs are higher than threshold then i have send a mail thats why i am looking to find out number of jobs in a queue
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Deleting a batch of print jobs

Hi Guys I have over 2000+ print jobs in one queue which I would like to delete. Is there away in AIX 4.3 that I can delete the whole print jobs at ocne. Instead of one at a time. Thanks (1 Reply)
Discussion started by: orvelb
1 Replies

2. SCO

Random duplicated print jobs

I have a weird problem, about 6 times a day a print job will be printed twice (out of more than 100 print jobs per day). It seems as though sometimes a print job is not cleared from the print spooler after the first print, and then reprints. This started a week ago after I had made printer... (1 Reply)
Discussion started by: Barry Staples
1 Replies

3. SCO

Print jobs getting stuck on the queue

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

4. HP-UX

Print Queue jobs stuck

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

5. UNIX for Dummies Questions & Answers

Catching print jobs.

Hi, I am wondering how to catch print jobs to process them before been served to the printer. I was told that the challenge is to catch raw text that an old legacy application sends to the printer (invoices, quotes, etc) and save them as text files to allow a new application to process them... (5 Replies)
Discussion started by: miguel77mex
5 Replies

6. Linux

holding print jobs in CUPS

Hi all. I have a problem with some printers that when I print a lot of jobs at once the printers gets stuck after 2 prints... (It's a barcode printers - DATAMAX). Whenever I'm printing each job separtly with a delay of a few seconds the printers work fine... So my question is how can I... (0 Replies)
Discussion started by: eliraza6
0 Replies

7. Shell Programming and Scripting

print queue jobs

Hi, I have one queue that have status QUEUE and 10 jobs are waiting.Can any one guide me how i can get total number of jobs on this queue.i can see 10 jobs but i need to get count 10 for this queue.Please help me out thanks in advance sagii (2 Replies)
Discussion started by: sagii
2 Replies

8. Shell Programming and Scripting

print queue jobs

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

9. UNIX for Advanced & Expert Users

[Solved] remove all print jobs from a print queue

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

10. AIX

Print jobs stuck in queue

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
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)
All times are GMT -4. The time now is 11:47 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy