Jump to content United States-English
HP.com Home Products and Services Support and Drivers Solutions How to Buy
» Contact HP
More options
HP.com home
HP-UX Reference > Q

queuedefs(4)

HP-UX 11i Version 3: February 2007
» 

Technical documentation

» Feedback
Content starts here

 » Table of Contents

 » Index

NAME

queuedefs — queue description file for at, batch, and crontab

SYNOPSIS

/var/adm/cron/queuedefs

DESCRIPTION

The queuedefs file describes the characteristics of the queues managed by cron (see cron(1M)). Each non-comment line in this file describes one queue. The format of the lines are as follows:

  • q. [njob j][nice n][nwait w]

The fields in this line are:

q

The name of the queue, such that a is the default queue for jobs started by at (see at(1)), b is the queue for jobs started by batch (see at(1)), and c is the queue for jobs run from a crontab file (see crontab(1)). Queue names d through y designate user-defined queues.

njob

The maximum number of jobs that can be run simultaneously in that queue. Although any number can be specified here, cron (see cron(1M)) by default limits the number of jobs that can be run on all the queues to 100. This limitation can be removed by setting the variable DISABLE_MAXJOB_LIMIT to 1 in the /etc/default/cron file.

nice

The nice value to give to all jobs in that queue that are not run with a user ID of super-user (see nice(1)). 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 more than 100 jobs were running in all the queues (see njob above).

EXAMPLES

Consider the following queuedefs file:

a.4j1n b.2j2n90w

The file is interpreted as follows:

a.4j1n

The a queue, for at jobs (see at(1)), can have up to 4 jobs running simultaneously, and those jobs will be run with a nice value of 1.

Since no nwait value is 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 (see cron(1M)).

b.2j2n90w

The b queue, for batch jobs (see at(1)), can have up to 2 jobs running simultaneously. Those jobs will be run with a nice value of 2. If a job cannot be run because too many other jobs are running, cron 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.

STANDARDS CONFORMANCE

queuedefs: SVID2, SVID3

Printable version
Privacy statement Using this site means you accept its terms Feedback to webmaster
© 1983-2007 Hewlett-Packard Development Company, L.P.