10-17-2008
Usually daily jobs run at 04:00. Have you checked your cron log to see what's being run around that time?
Try running top in batch mode overnight and examine the output the following morning to figure out what's causing the slow down. See man top for the details.
9 More Discussions You Might Find Interesting
1. Solaris
Hi, im very newb in Solaris. I have install So10. Now i just try install the first software Midnight Commander and fails. I just do as follow
- i go to Sunfreeware - Freeware Open Source Software for Sun Microsystem's Solaris and get into x86-so10 link ( i use VM ware ) download these packages... (5 Replies)
Discussion started by: tien86
5 Replies
2. SCO
After System power get failed
File system is not getting mounted in read- write mode (1 Reply)
Discussion started by: gtkpmbpl
1 Replies
3. UNIX for Dummies Questions & Answers
When running MC in xterm or gnome-terminal, it doesn't seem to allow the use of Ctrl-enter and Ctr-shift-enter to copy marked files to the command line.
Does anyone know of another way to cause this to happen or a way to enable it under xterm/gnome-term?
With thanks,
Narnie (0 Replies)
Discussion started by: Narnie
0 Replies
4. UNIX for Advanced & Expert Users
Hi,
In order to have a sand box machine that I could use to test some system changes before going to production state, I'd like to duplicate a working system to a virtual one. Ideally, I'd like to manage to do it this way :
- Make a full system backup excluding the user file system (this... (7 Replies)
Discussion started by: pagaille
7 Replies
5. Fedora
We've been having issues for about a year, although thankfully they are in-frequent and randam. Meaning it happened a couple of times within a 3 month period, then stopped for a couple of months and then started again. It has happened twice now in the last month. At the stroke of midnight, ... (5 Replies)
Discussion started by: graybeard
5 Replies
6. Shell Programming and Scripting
Hi Guys,
I am having a brain freeze....
I want to monitor a directory for a time stamped file on a sol 10 system in bash or ksh, the files will come in looking like this..
randomfile.DDMMYY.rpt
The problem i am having is the file can come in before or after midnight, the file will... (5 Replies)
Discussion started by: twinion
5 Replies
7. Shell Programming and Scripting
Hi there!
I was wondering if someone could help me with the following:
I'm trying to find all files within a directory which have been modified since midnight of the current date.
Any help would be appreciated.
Thank you kindly. (6 Replies)
Discussion started by: Jimmy_the_tulip
6 Replies
8. AIX
Hello All,
I am trying to clone an entire AIX virtual machine to a new virtual machine including all partitions and OS.Can anyone help me on the procedure to follow? I am not really sure on how it can be done.Thanks in advance.
Please use CODE tags for sample input, sample output, and for code... (4 Replies)
Discussion started by: gull05
4 Replies
9. UNIX for Beginners Questions & Answers
In a nutshell requirement is to migrate the system from mainframe environment to UNIX environment (MF cobol would be used I guess). I have not much of idea in this field. I need to do some investigation on following points -
- Ease of conversion
- Known Data compatibility issue
- Issue in... (9 Replies)
Discussion started by: Tjsureboy4me
9 Replies
LEARN ABOUT X11R4
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)