10-24-2008
Did you add this cron job yourself, or did you just use the one that was installed by sysstat (usually in /etc/cron.d/sysstat)? Maybe there's another job running that's recording data every 10 minutes.
You shouldn't see 3 entries every x minutes anyway... the 3 just means that it should write 3 entries 20 minutes apart. i.e. first cron job of the day runs at 08:00, collects data for 1200 seconds, writes an entry, collects data for 1200 seconds, writes second entry, collects data for 1200 seconds, writes third entry and exits... at which time it would be 09:00 when the next cron job kicks in and repeats the exercise.
So the only mystery here is why it's recording at 10 minute intervals... unless sar insists on reporting in 10 minute intervals by default, but I didn't think it could do that unless the data was actually recorded with that frequency.
9 More Discussions You Might Find Interesting
1. Solaris
Dear All,
Where can i get the Sun Solaris 10 ( SA 1,2, and 3) in pdf ? (4 Replies)
Discussion started by: viswanadhan
4 Replies
2. AIX
Hi all, does anyone know what is the relationship between sa1 and sa2? Apparently both have to be included to make reporting work. If you include only 1, let's say sa2, the file is created but there's no content inside. Can someone shed some light and also provide examples of sa1 and sa2? Thanks a... (0 Replies)
Discussion started by: smallbook
0 Replies
3. Shell Programming and Scripting
I want to check process status at regular interval of time ...
so i ha wirtten this BUT its not working when i placed this peace of code in .sh ..
please help me out
#!/bin/sh
w = ps -ef|grep processname | wc - l
echo $w
if ; then
Banner "Proceesname Problem"
else
Banner " Running... (5 Replies)
Discussion started by: srinivasvandana
5 Replies
4. UNIX for Dummies Questions & Answers
Hi,
I want to generate gnuplot graph from sar data. My problem is the time format.
1- Gnuplot doesn't support the sar format (01:00:59 AM/PM)
2- Sar doesn't provide a switch to choose the format. The only way to do it is by exporting LANG=fr_FR.
Since I have other apps running and... (0 Replies)
Discussion started by: foxmtl
0 Replies
5. Shell Programming and Scripting
I have a backup folder that has sub folders created daily. Each sub-folder contains files for that specific day. I need to search all those files to see which ones contains a specific phrase. I also need to take that phrase and output to a text file for that day. This can be done with a one liner,... (3 Replies)
Discussion started by: bbbngowc
3 Replies
6. Shell Programming and Scripting
Hi,
i have csv input file looks like below
3rd field is date and time field i want to change it with user supplied date and time says
year=2011
month=09
day=05
hour=11
count=2
when count is say 10 then first ten records should pick and it should increment the... (2 Replies)
Discussion started by: raghavendra.nsn
2 Replies
7. Solaris
Hi
I've found this crontab entry to run sa1 on sunOs box but I don't know where the result of this command is being stored. Is there a standard location for this? I assume the command is supposed to be storing the details somewhere..
Thanks (2 Replies)
Discussion started by: Grueben
2 Replies
8. Shell Programming and Scripting
I have a list of epoch times delimited by "-" as follows:
1335078000 - 1335176700
1335340800 - 1335527400
1335771300 - 1335945600
1336201200 - 1336218000
The corresponding dates are:
20120422 1000 - 20120423 1325
20120425 1100 - 20120427 1450
20120430 1035 - 20120502 1100 ... (3 Replies)
Discussion started by: alex2005
3 Replies
9. OS X (Apple)
Hi guys and gals...
I am writing a piece of code that is dash compliant and came across this error.
I have put it in the OSX section as that is what I am using.
I have no idea what the 'dash' version is but was installed about 6 months ago.
MBP, OSX 10.12.6, default terminal running dash on... (4 Replies)
Discussion started by: wisecracker
4 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)