06-13-2006
something
something similar here
see here
Regards.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
hi
can someone help me to write a script to monitor the growth of the directory running at 5 hours interval and then pipe it to a file :(?
i only know the manual command "du -sk"
and the worst i dun know anything about script. (3 Replies)
Discussion started by: legato
3 Replies
2. Solaris
Hi,
I want to write a script that will monitor cpu,mem usage and disk usage for entire day and data will be redirected to file, (4 Replies)
Discussion started by: manoj.solaris
4 Replies
3. Shell Programming and Scripting
Dear All,
I am new to Shell Programming, but I need a script which will monitor the different IP's in the live logs.
Condition:-
The script will monitor the logs continously and should print only those IP's which exists more than 3 times per day.
Please do help me.
Thanks and... (1 Reply)
Discussion started by: akhtar.bhat
1 Replies
4. Shell Programming and Scripting
I have to monitor several processes in my application .
i get the listing of these processes using the command ps -ax
i want to write a shell script that will monitor the processes and if a
process goes missing then it will send an email to my gmail account.
I want to run this... (6 Replies)
Discussion started by: asalman.qazi
6 Replies
5. Shell Programming and Scripting
Hi Experts,
I need a script advice to schedule 12 jobs ( SAS Codes execute back ground ).
Algorithem:
1. Script checks first job.
2. Finds first job is done; invoke second job.
3. finds second job is done; invoke third job.
..
Request you to please assist. (3 Replies)
Discussion started by: Jerald Nathan
3 Replies
6. UNIX for Advanced & Expert Users
Hi
I do a very simple monitoring of our OpenLDAP (runs in cronjob and generate alerts if unsuccessfull)
$ ldapsearch -h hostname.domain -D "cn=monitor_user,ou=People,dc=organisation" -w "password" -b "dc=organisation" -x "(&(cn=monitor_user)(ou=People))" dn | grep -v version
dn:... (4 Replies)
Discussion started by: slashdotweenie
4 Replies
7. Shell Programming and Scripting
I currently have a shellscript to check the size of a filesystem and email me if the size is over a certain percentage (80%). I have this script on crontab and executes the shell every 10 mins.
I have the above in place on 8 servers. It so happens that a file system on one of the servers is... (1 Reply)
Discussion started by: goddevil
1 Replies
8. Shell Programming and Scripting
Hi,
I have a project which i need to automate some manual work. We have a 100 jobs in Linux and Unix environment. We do job monitoring daily. that is taking more that 2 to 3 hrs for us because we use autorep -j <jobname> command for each and every job. That takes more time for us to do.
We have... (16 Replies)
Discussion started by: cg_saran
16 Replies
9. Shell Programming and Scripting
Hi
I have a requirement to write a shell script,that will check the all commented job in cron job.Please help !! (2 Replies)
Discussion started by: netdbaind
2 Replies
10. What is on Your Mind?
Hi guyz,
Please send me a script which is to be sending an automatic email to particular mail id's when a job get complete with status successful.
Please send me your script to my mail id : rehan.csjmu@gmail.com
Thanks in Advance.
---------- Post updated at 11:33 AM ----------... (1 Reply)
Discussion started by: Rehan Ahmad
1 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)