What are the rules of calling shell scripts in cron.
How do I go about setting up the correct PATHS that calls a script, which then calls another sub script all of which has to retain the orginal PATHS and VARS that I've set up in first script
Confused..
ok
Well Cron calls a script... (3 Replies)
Hi,
can we have more than one cron in the shell script? If so pls let me know on what basis it is running. Whether on OS scheduling or the time scheduled in the cron file.Pls answer this query.
Many Thanks (4 Replies)
Dear Experts,
I have a script defined in Cron which runs every 1 minute.
* * * * * /export/home/myscript.sh >/dev/null 2>&1
Now the issue is executing that myscript.sh sometime will take 2/3 or more minutes to finish execution.
But after 1 minute cron will invoke another... (4 Replies)
Hey Guys,
i was trying out a shell script which has to remove a file for every 90 mins. this is the code i came up with .
$ crontab -e file1
file1 contains
30 1 * * * * rm -r /folder1/folder2/somefile.txt
Now i need the cron to run for every 90 mins. the problem with this is... (8 Replies)
Hello,
I know little about shell scripting and creating a script, and worked fine in the command line. But not work in the cron. Below you could see the script
#!/bin/sh
LOGFILE=/home/transfield/mou/test.log
# Find yesterday Date and copy files
TODAY=$(date --date= +%F)
YESTERDAY=$(date... (4 Replies)
Hi there,
I have a script that pulls in a weather feed via FTP then writes the output to a file.
This script is run everyday at 3pm by cron.
Heres the shell script:
#!/bin/sh
HOST='ftp.weatheronline.co.uk'
USER='my username'
PASSWD='my password'... (2 Replies)
hi...
im quite new in unix
been using it for 2 years
i got a job to monitor error/failure
my question is which is better to do a routine job
crond / shell script
the idea is to put all the command and make it append all the output to a txt/log file
tq in advance (3 Replies)
How can I tell a script to only execute if the other scripts exits successfully?
So "script A" executes and if it executes successfully (0),then "script B" will run
or else
"script A "executes and it exits unsucessfully (1) then "script B" will read return code (1) and will not execute
... (3 Replies)
Hi freinds,
I have tried running a script through cron ,it is a shell script which calls a oracle procedure , problem here is that there is function in sql code which makes a external C call , this function is failing when running manually but works when run manually.
I have trouble shooted... (6 Replies)
Hi everyone,
I'm doing a small project for my scripting class using cron and I've come to a point where I can't get the last echo command to work at all. I would like it to create a file in the /watcher folder with the given information and also, just to clarify, print the same time and date from... (3 Replies)
Discussion started by: millanboy
3 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)