12-05-2001
By default, the at command will queue jobs in the at-jobs queue, queue a. Queue b is for batch jobs. Queue c is reserved for cron jobs and can't be used with at. Unless you have set up a special batch queue and use the -q b option to the at command, all at jobs go into the at-jobs queue until they are executed. When the job is executed it is no longer in a queue. It is now an executing job and can be seen using ps -ef (or -al depending on the UNIX flavor you are running).
If you have set up a batch queue for command processing, most flavors of UNIX implement this under the print queueing system so you use the lpstat, lpq, etc. commands depending on your UNIX flavor.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I have a print queue set up with the following options: remote, standard processing, Hostname=(A Windows 2000 Server), bsd print spooler. It takes about 1 minute to transfer a 100 kb file and it times out (downs the queue) on larger files. When tested on a different system at a different location... (2 Replies)
Discussion started by: Scottb7711
2 Replies
2. Linux
RH 7.2
Are there any commands to check the print queue status? Something along the lines of AIX's "qchk"?
Thanks!! (2 Replies)
Discussion started by: jalburger
2 Replies
3. Programming
Hi all,
I've been trying for hours to figure out how to turn my 2-program (one to send and one to receive) "chat system" using message queues, into a single program where each concurrent component (entity) will both send and receive messages. PLEASE give me a hand with this, I'm starting to... (9 Replies)
Discussion started by: mgchato
9 Replies
4. UNIX for Dummies Questions & Answers
let 3 processes a, b and c are sharing msgs using msg queues.process 'a' sending msg to 'c' and in turn 'c' send sthat msg to 'b'.if something happens to c how can 'a' and 'b' know that 'c' is not available?????? (2 Replies)
Discussion started by: sukaam
2 Replies
5. BSD
Hi! Everybody%)
I got a question like this: Does my FreeBSD5.1 support Posix queues.
Thanks! (7 Replies)
Discussion started by: kamazi
7 Replies
6. Programming
hi
I am using posix functions such as mq_open, mq_close and including the mqueue.h. but its giving a linking error,"undefined reference to mq_open and mq_close".
it it that we have to link some library or so while compiling... plzzz help
Thanxs
Mohit (0 Replies)
Discussion started by: mohit3884
0 Replies
7. UNIX for Advanced & Expert Users
#include <sys/ipc.h>
#include <sys/msg.h>
int main()
{
int qid;
int t;
struct msgbuf mesg;
qid=msgget(IPC_PRIVATE,IPC_CREAT);
mesg.mtype=1L;
mesg.mtext=1;
t=msgsnd(qid,&mesg,1,0);
printf("%d",t);
}
the program prints -1 as the result of msgsnd ,which means that msgsnd doesn't... (1 Reply)
Discussion started by: tolkki
1 Replies
8. UNIX for Dummies Questions & Answers
can any body provide a tutorial that explains the concept of message queues in UNIX in great detail (1 Reply)
Discussion started by: asalman.qazi
1 Replies
9. Programming
I have a problem understanding the different scheduling queues (Ready Queue, I/O Queue, Job Queue) Can you please explain/illustrate/differentiate these queues to me? Thanks a lot guys.;) (1 Reply)
Discussion started by: zel2zel
1 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)