02-04-2014
for every 2 minutes in a day zaxxon
7 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
I apologise because I had pasted this question in the newbies forum first (because i am a bit of a newbie) but thought it might be better suited in here
if i have to sepearate parameters can I use this syntax especially the or part (||) and is this correct
if (6 Replies)
Discussion started by: w33man
6 Replies
2. UNIX for Dummies Questions & Answers
What this command sed "/*$/d" means?
izzit add commas to numeric strings, changing "1234567" to "1,234,567" ? (1 Reply)
Discussion started by: rita1985
1 Replies
3. Programming
for a floating-point array x whose size is n, find the geometric mean..
GM =n x1.x2.x3...xn (2 Replies)
Discussion started by: allyjaah
2 Replies
4. Shell Programming and Scripting
I have the following Phyton script and want to print something if the option was selected
For example if the user uses --npop=12, I want to check if the user has inputted --npop and
do
if npop selected, print npop
Or if the user puts --fdata=npt02.dat I print something like
if fdata... (3 Replies)
Discussion started by: kristinu
3 Replies
5. Shell Programming and Scripting
HI,
Can some one guide me how to make changes to the script below so that it can load the history of a program to IT server ?
Format of data:
YYYYMMDD065959.dsk.log
YYYYMMDD235959.dsk.log
currently both are loaded together. Need to separate them as above format.
Thanks in advance.
... (1 Reply)
Discussion started by: crazydude80
1 Replies
6. Windows & DOS: Issues & Discussions
HI,
Can some one guide me how to make changes to the script below so that it can load the history of a program to IT server ?
Format of data:
YYYYMMDD065959.dsk.log
YYYYMMDD235959.dsk.log
currently both are loaded together. Need to separate them as above format.
Thanks in advance.
... (2 Replies)
Discussion started by: crazydude80
2 Replies
7. What is on Your Mind?
"Naive coding."
(Apologies for any typos.)
I came across this phrase a couple of weeks ago and it has made me decide to set off a discussion.
I had never heard of it before but I did some research and discovered that I probably fall into this category.
My phrase is: "I code to work, not... (10 Replies)
Discussion started by: wisecracker
10 Replies
LEARN ABOUT OPENSOLARIS
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.11 1 Mar 1994 queuedefs(4)