08-03-2009
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I've got an *extremely* simple script I want to run every minute:
#!/bin/sh
ping -c 1 192.168.1.20 > ~/onlinestatus.txt
So, the script is called "status", it's executable, and in the correct path, etc. In a terminal window (I'm using Mac OS X), I can type status, and it will create... (4 Replies)
Discussion started by: jmf77
4 Replies
2. Solaris
I have a cron job set to run a script everyday. If I run the script out side of cron it runs correctly. If cron runs the script is produces a 0 byte file and it puts the output in the / directory. The script is set to put the output in a specific directory. Any help would be appreciated. (8 Replies)
Discussion started by: mbattreall
8 Replies
3. Shell Programming and Scripting
Hi guys with regards to Cron jobs if for example i run a script and it produces output to the admin mail how could i stop it from doing that at script level and redirrect it to a file so that admin does not have all these emails about jobs done correctly. (4 Replies)
Discussion started by: musicmancanora
4 Replies
4. Shell Programming and Scripting
I can call a C program from the shell and results are outputted as normal. The C program processes some files and spits out a .csv file.
If I scheduled it in cron, there is no output.
If their a special way to schedule C programs in cron?
thanks & regards (1 Reply)
Discussion started by: hazno
1 Replies
5. Red Hat
I have the following cron task set to run every 15 minutes to ascertain how many users are in the system and append the result to the log.
/home/pronto/cus/whoisinc >> /home/pronto/cus/whoisin.log
This is the whoisinc script
date +"%d-%m-%Y,%k:%M,Pronto Users,`prowho -s | grep -v... (1 Reply)
Discussion started by: scottm
1 Replies
6. Solaris
Hi,
I have issue with cron.
When i run script manually output is fine but when i add it to cron output file is not as same.
both file attach some junk charecter comming in cron output.
thanx
Jignesh (5 Replies)
Discussion started by: jkmistry
5 Replies
7. Shell Programming and Scripting
Hello,
This may be a simple one, but i can't see what the issue is.
When i run the script via CLI, then i get the correct output via the if statement, but when i run via CRON i get the wrong statement.
echo " Checking Job Status" >> $DIR/Bpimagecleanup_$DATE... (3 Replies)
Discussion started by: Junes
3 Replies
8. Shell Programming and Scripting
Hi All,
I am running the below shell script through cron and surprisingly it gives different output
$uname -a
Linux 2.6.18-194.3.1.7.3.el5xen #1 SMP Fri Jul 30 00:08:45 EDT 2010 x86_64 x86_64 x86_64 GNU/Linux
$ echo $SHELL
/bin/bash
shell script:
cat sar_cpu.sh
#!/bin/bash
... (10 Replies)
Discussion started by: a1_win
10 Replies
9. UNIX for Advanced & Expert Users
Hi All,
I have a script which checks the status of HP Smart Array & then emails me the output.
The script run fine when executed manually but I receive no output when configured in a cron job.
The script is below:
hpacucli ctrl slot=3 show config | mail -s "ARRAY STATUS-`date`"... (6 Replies)
Discussion started by: coolatt
6 Replies
10. Shell Programming and Scripting
Hi
Does anyone have any suggestions for capturing the output into a file when i run it through cron?
I have file called "quick.1" which contains two simple commands to be executed on the target host. And i have second file called "quick.2" which contains the wrapper script to ssh to the target... (1 Reply)
Discussion started by: chandika_diran
1 Replies
LEARN ABOUT PHP
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)