08-16-2002
Problem with crontab
I am trying to schedule a job to run through cron that checks for high CPU usage. The 'top' command is run and the output is logged to a file. A calculation is done in the file to check if CPU runs above 80%. If this happens an email is sent out.
The problem I am having is that when I run this manually from the command prompt is runs fine. When I run it through cron it doesn't output teh results of the 'top' commnad to the file. Does anybody know why this would happen? The script uses awk commands as well. Any help will be appreciated.
Thanks
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I trying to include a script in my crontab as user. I used "crontab -e" to include my script there but does not seem to work. If I understand correctly it is set to run at 11:20 every day, correct?
Can anybody identify any error?
<pre>
#Sun Microsystems Inc. SunOS 5.7 Generic... (19 Replies)
Discussion started by: guest100
19 Replies
2. Shell Programming and Scripting
HI,
i am working on linux.
i have crontab problem
i wrote a small script and put it in a crontab .
but the script is not running..
i have given following way in crontab -e
02 06 * * * /bin/csh /home/vr_test.csh
but the above script is not running
please rectify my... (26 Replies)
Discussion started by: rajan_ka1
26 Replies
3. UNIX for Dummies Questions & Answers
I'm trying to get crontab to run a script, but to test crontab I tried out a very simple command: `echo bob`
here is my crontab file (I edited it by using `crontab -e`):
-----------------
#!/bin/sh
23 10 * * * echo bob
and at 10:23 every day I get a new message:
in /var/mail/a... (3 Replies)
Discussion started by: cleansing_flame
3 Replies
4. UNIX for Dummies Questions & Answers
i added to my crontab file:
* * * * * echo "hello"
it works, i receive a message into my /var/mail/username
and i receive: bob
in addition to a large text add-on
any help appreciated (1 Reply)
Discussion started by: cleansing_flame
1 Replies
5. UNIX for Advanced & Expert Users
hi all
while using crontab -e im receiving
754 as output
im unable to add a entry in crontab
crontab -l is working fine
OS: sun5.8
can some one please assist me (4 Replies)
Discussion started by: NIMISH AGARWAL
4 Replies
6. Shell Programming and Scripting
Dear All ,
I have .sh script wich has the following inside
getFileName=Listportfolio.txt.`date +'%Y%m%d`
ftp -n 172.10.10.1<<EOF
user xxx xxx
bin
cd /home/gbs/FTP_Script
get /home/gbs/FTP_Script/$getFileName
bye
EOF
EOF
when I run the... (3 Replies)
Discussion started by: habuzahra
3 Replies
7. Shell Programming and Scripting
Hi All,
Am facing an issue while updating the crontab.Getting below error while updating the cron.
cron/tmp.XXXX5fXBR6: No space left on device
crontab: edits left in /tmp/crontab.XXXXEJX5gw
Is there any file where i need to alter using root user so that i can update the cron.
TIA... (9 Replies)
Discussion started by: Ashok_oct22
9 Replies
8. AIX
Hi to all.
Guys, i have a truble with oracle user crontab.
He work if i'm do
0-59 * * * * echo LOL> ~/test.txt
But not work if me set realy norm date
For example
14 17 28 12 * echo LOL> ~/test.txt
In 17:14 28 December .
In log file /var/adm/cron/log nothing....
Please... (3 Replies)
Discussion started by: jess_t03
3 Replies
9. UNIX for Advanced & Expert Users
hi..
i have a program (tf.sh), and i want what it runs automatically with a "lapsus" of 2 hours. (1,3,5,7,9,11,13,15,17,19,21,23 hrs.)
i know what i have to do it using crontab, but i donīt know how to do it.
i have the next idea, but the problem is what it doesnīt run on my server... (11 Replies)
Discussion started by: DebianJ
11 Replies
10. Solaris
hi all
does any on has explanation for this result
bash-3.00$ crontab -e
"/var/tmp/Ex1kayUW" No space left on device
The crontab file was not changed.
bash-3.00$ (2 Replies)
Discussion started by: osmannix
2 Replies
LEARN ABOUT OSF1
queuedefs
queuedefs(4) Kernel Interfaces Manual queuedefs(4)
NAME
queuedefs - Queue description file for at, batch, and cron commands
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron or specifies other characteristics for cron. Each noncom-
ment line in this file describes either one queue or a cron characteristic. Each uncommented line should be in one of the following for-
mats.
q.[njobj][nicen][nwaitw] max_jobs=mjobs log=lcode
The fields in these lines are as follows: The name of the queue. Defined queues are as follows: The default queue for jobs started by at
The default queue for jobs started by batch The default queue for jobs run from a crontab file
Queues d to z are also available for local use. The maximum number of jobs that can be run simultaneously in the queue; if more
than njob jobs are ready to run, only the first njob jobs will be run. The others will be initiated as currently running jobs ter-
minate. The nice(1) value to give to all jobs in the queue that are not run with a user ID of superuser. The number of seconds to
wait before rescheduling a job that was deferred because more than njob jobs were running in that queue, or because the system-wide
limit of jobs executing (max_jobs) has been reached. The maximum number of active jobs from all queues that may run at any one
time. The default is 25 jobs. Logging level of messages sent to a log file. The default is 4. Defined levels are as follows:
level-code level
0 None
1 Low
2 Medium
3 High
4 Full
Lines beginning with # are comments, and are ignored.
EXAMPLES
The following file specifies that the b queue, for batch jobs, can have up to 50 jobs running simultaneously; that those jobs will be run
with a nice value of 20. If a job cannot be run because too many other jobs are running, cron will wait 60 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. If a job cannot be run
because too many other jobs are running cron will wait 60 seconds before trying again to run it. b.50j20n60w
The following file specifies that a total of 25 active jobs will be allowed by cron over all the queues at any one time, and cron will log
all messages to the log file. The last two lines are comments that are ignored. max_jobs=25 log=4 # This is a comment # And so is this
FILES
Main cron directory The default location for the queue description file.
RELATED INFORMATION
Commands: at(1), cron(8), crontab(1), nice(1)
delim off
queuedefs(4)