The problem is solved. The thing is that emcast expects data on stdin, on cron there is no terminal, and it founds no data on stdin and finishes execution. emcast has option quiet -q which tells emcast not to read from stdin, but then there is no output on stdout (which is not good in my case because i use pipe on output), so code of emcast needs to be changed in oreder to add half quiet mode that does not read from stdin but writes on stdout.
Hi,
I have a cron schedule like this
04,16,28,40,52 * * * * /nag/startProcessABatch (unix script)
i want to add new lines in this file (like Logging), i just copy this file into a /tmp folder (for backup copy), and i have edited this file (added few lines of code for logging).
... (1 Reply)
Hi,
I am facing this problem . My Cronjob entry is not running !!!
I am having Sun solaris 9 and cronjob entry is
"45 1 * * * /safedir/rdns/opt/RDNS1.1Scripts/drpl_audit_log_script.sh_orig > /dev/null 2>&1"
Now when I try to look in the output log files it creates, it is some file with... (1 Reply)
hi,
i have the following line in the crontab
15 5 * * 6 /home/adw/BCE_ADW.pl
The problem is the cron job is not getting started automatically.
But this was working til last week. now it is not working.
what could be the problem. Any idea? (3 Replies)
am running a cron job to do a backup of all user files. the script runs properly in the terminal but only backups about 20% of the files when run by cron.
the Linux system is running BASH as far as I can tell.
the symbols $FILE and $DIRECTORY are defined properly and the following is the... (1 Reply)
Hi All,
I am editing crontab using -e option to add a new job
Below is the line
30 * * * * scriptpath
This job is not executing every thirty minutes.
I have checked, cron daemon is running.
What did I miss? Can some one help?
I am using cron shell..ksh (7 Replies)
Hi,
I have scheduled a job previously and was running fine,but due to some issue i have commented it.Now the issue was solved and i have scheduled as below in crontab.
30 2 * * * /u01/srcdata/CSA/holding/common/script/QPLR_RegValrao.sh PROD
Cron is running,but my job is not triggering.
... (1 Reply)
Hi,
I have set up the crontab as follows.
root@IDC4VASAPP07 # crontab -l
0-59 * * * * /var/tmp/r.sh
0-59 * * * * date >> /var/tmp/log
root@IDC4VASAPP07 #
r.sh is as follows.
root@IDC4VASAPP07 # cat r.sh
#!/bin/bash
dt1=$(perl -e 'use POSIX;print strftime... (10 Replies)
Hi ,
I have removed a cron for particular user , but cron job seems to be running even after the cron entry is removed. The purpose of the cron was to sendmail to user ( it uses mailx utility )
I have restarted cron and sendmail service still user is getting mail alerts from the cron job. And... (4 Replies)
Hi All,
I am writing a script that will eventually be executed by a cron job every 15 minutes. I want to make sure that my logic/script doesn't get executed if a previous job is still running. What would be the best way to handle that scenario? I was thinking to make my script create a temporary... (1 Reply)
Scheduled job is not running on time.but it is running when executing same command manually.
25 10 * * * /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Manually executing the same
Ksh -x /code/bin/ACCOUNT.ksh 1 >/dev/null 2 >&1
Followed steps
Crontab -e
Added the job to cron tab. (4 Replies)
Discussion started by: Myguest
4 Replies
LEARN ABOUT PLAN9
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)