10-06-2004
Quote:
it was working fine for 3 months and all of suden it stops executing
Find what changed. Either permissions on the directories ( /v/sysadmin/sysnet/ ), crontab file (could have an error on that line that you don't realize), permissions for the user running the cron job (if not root - acl's put in place... ).
I would not think if it WAS working, that insuring the environment is set will do any good - you probably had that straight before (double check that no one changed your .profile or the system profile).
Can you find any error messages in log files? cron.log, messages, ... Post your OS/version for more assistance on that.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Hi , I write a script like this\ and put it under / (root) :
ref=88
df -k | grep /cbmdata/00/gdd | tr -d '%' | \
while read a b c d e other
do
if (( $e >= $ref ))
then
line=`find /cbmdata/00/gdd -name "LOGS*" |sort -nr |tail -1`
# echo $line
rm -f $line
fi
done
... (11 Replies)
Discussion started by: xramm
11 Replies
2. UNIX for Dummies Questions & Answers
Hi all
Recently i had finished a perl script. When i run manually, the script work fine.
But when i wanted to put the script in cron, it didn't get the same output as it run manually. I felt that it only execute the script until certain line then it stop as i see most of the related files didn't... (6 Replies)
Discussion started by: AirWalker83
6 Replies
3. Shell Programming and Scripting
Hi,
I want to schedule a job to run every 15 mins through cron.
searched the forums and came up with this piece of code.i have given this in my crontab
0-59/15 * * * * sh /usr/ss/job
But its not being run. Have i made any mistake here.
Can any1 post the cron code for scheduling the... (5 Replies)
Discussion started by: suresh_kb211
5 Replies
4. Shell Programming and Scripting
Hi!
I have a svn backup script that works perfectly if I execute it from the command line but if I set it as a cronjob to run at night, only part of the code works.
So, basically the scripts starts by deleting the folder yesterday and then moves the folder today to the folder yesterday. When... (4 Replies)
Discussion started by: ruben.rodrigues
4 Replies
5. AIX
In my cronjob, I would like to schedule my script.sh to run every minutes. I crontab -e and have in line below but it didn't seems to run at all.
* * * * * script.sh
When I run it manually, I can run it. Is that anything wrong with the above line?
If I change it to something like below,... (4 Replies)
Discussion started by: ngaisteve1
4 Replies
6. Shell Programming and Scripting
Hi All ,
Please read the below data carefully.
I have run the below script on unix server its running succesfully. but when i run the same script using cronsetyp it giving me the error :
command not found at (line num):cruiseStartup.sh
below is code
netstat -anp |grep 8181... (5 Replies)
Discussion started by: aish11
5 Replies
7. UNIX for Dummies Questions & Answers
Hello,
I am new to cron. I have a cronjob that updates a dataset in a 3rd party application. The contents of this dataset come from a text file, which is updated irregularly. Currently my cronjob runs once every week, to update this dataset (irrespective of whether the file was updated or not).... (7 Replies)
Discussion started by: ad23
7 Replies
8. Shell Programming and Scripting
Hi,
I would like to ask some few questions about zenity. I write a script that would generate a report if any changes on the files. i want to used zenity to had a visual alarm report if theres some changes on the comparisons of the file.I used this line of zenity but it doesn't work in cronjob.... (5 Replies)
Discussion started by: jao_madn
5 Replies
9. Shell Programming and Scripting
Hi Friends,
I have a requirement to run the cronjob for every 10 minutes from 2:00 AM to 6:00 AM. Does the below code works? If not, please advise.
* * * * * command to be executed
┬ ┬ ┬ ┬ ┬
│ │ │ │ │
│ │ │ │ │
│ │ │ │ └---------------------------------- day of week (0 - 6) (0 is... (5 Replies)
Discussion started by: srikanthbiradar
5 Replies
10. Shell Programming and Scripting
Hi
I'm having hard time here with below script. If i run script manually i see expected results but, if i keep this script in cron job i'm getting unexpected results. Unexpected results means even though condition is true,cronjob returning output of else condition.
This script and cronjob... (2 Replies)
Discussion started by: buzzme
2 Replies
LEARN ABOUT SUNOS
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)