Sponsored Content
Full Discussion: vb 3.0 Upgrade Discussion
Contact Us Post Here to Contact Site Administrators and Moderators vb 3.0 Upgrade Discussion Post 60225 by google on Thursday 13th of January 2005 07:51:34 AM
Old 01-13-2005
Not sure I like this validation queue, though I think I understand its purpose. But still, I would like to see my posts show up right away rather than have to wait to see them. Somewhat annoying.
 

2 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

Kill script discussion

Does anybody got an idea to write a script to kill a long list of processes automatic? I got try this: ps -ef | grep 'my_name' After that, I used the "kill -9 PID". It seems like quite inefficient if I got a long list of processes need to terminate or kill it :( Thanks a lot for any... (2 Replies)
Discussion started by: patrick87
2 Replies

2. What is on Your Mind?

Discussion culture

I want to start a small thread about discussion culture. From the past experience in different fora, I have little hope that any will come out of it. But I'll try it anyway, hoping to contributing to an improvement on the topic. I do not want to discuss a specific technical question, but only... (5 Replies)
Discussion started by: stomp
5 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 01:56 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy