06-09-2011
Check what cron is running
How to check what cron is scheduled to run? I don't want to modify anything. Thanks
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
I am running a script by scheduling it using the cron. The line in the cron file is -
10 * * * * ksh -v /apps/gofis/svam/cos_automation/cos_automation.sh vpqa > /apps/gofis/svam/cos_automation/cron.log 2>&1
But after the job is executed, the cron.log contains some part from... (4 Replies)
Discussion started by: ankurgupta
4 Replies
2. UNIX for Advanced & Expert Users
I have written a shell script and when i run it from shell prompt it runs fine but in the cron it only runs partially.
That means cron is working fine.
there is a command which i am using in the script which doesn't run at all.
That comman uses different user privileges like ptadmin
i am not... (4 Replies)
Discussion started by: ajnabi
4 Replies
3. HP-UX
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)
Discussion started by: nag_sundaram
1 Replies
4. UNIX for Advanced & Expert Users
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)
Discussion started by: Suguna
3 Replies
5. Shell Programming and Scripting
i have a simple script that ftp a file out, manually running it works fine.
#!/bin/sh
ftp 152.226.69.48 << cmd
bin
get applicant_vw.txt
quit
cmd
but when I cron it,
14 9 * * * /opt/home/XXX/XXX/dailyjob.sh > /opt/home/XXX/XXX/cronlog.txt
seems that it was executed because i can... (2 Replies)
Discussion started by: beisaikong
2 Replies
6. UNIX for Advanced & Expert Users
Hello All,
I have installed a few crons on a machine. But for some reason the crons just don't run. I have checked the permissions on the files and also restarted the cron daemon. But it doesn't seem ti help. Can anyone suggest any other things I can do to get it running again?
Regards,... (6 Replies)
Discussion started by: garric
6 Replies
7. UNIX for Dummies Questions & Answers
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)
Discussion started by: yabhi_22
7 Replies
8. Solaris
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)
Discussion started by: SunilB2011
10 Replies
9. Solaris
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)
Discussion started by: chidori
4 Replies
10. Shell Programming and Scripting
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)
Discussion started by: rdogadin
1 Replies
CRON(8) BSD System Manager's Manual CRON(8)
NAME
cron -- daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-n] [-x debugflags]
DESCRIPTION
cron is normally started during system boot by rc.d(8) framework, if cron is switched on in rc.conf(5).
It will return immediately so you don't have to start it with '&'.
cron searches /var/cron/tabs for crontab files which are named after accounts in /etc/passwd. Crontabs found are loaded into memory. cron
also searches for /etc/crontab which is in a different format (see crontab(5)). Finally cron looks for crontabs in /etc/cron.d if it exists,
and executes each file as a crontab.
When cron looks in a directory for crontabs (either in /var/cron/tabs or /etc/cron.d) it will not process files that:
- Start with a '.' or a '#'.
- End with a '~' or with ``.rpmsave'', ``.rpmorig'', or ``.rpmnew''.
- Are of zero length.
- Their length is greater than MAXNAMLEN.
cron then wakes up every minute, examining all stored crontabs, checking each command to see if it should be run in the current minute. When
executing commands, any output is mailed to the owner of the crontab (or to the user named in the MAILTO environment variable in the crontab,
if such exists).
Events such as START and FINISH are recorded in the /var/log/cron log file with date and time details. This information is useful for a num-
ber of reasons, such as determining the amount of time required to run a particular job. By default, root has an hourly job that rotates
these log files with compression to preserve disk space.
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab or /etc/cron.d) has changed,
and if it has, cron will then examine the modtime on all crontabs and reload those which have changed. Thus cron need not be restarted when-
ever a crontab file is modified. Note that the crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
The following options are available:
-x This flag turns on some debugging flags. debugflags is comma-separated list of debugging flags to turn on. If a flag is turned on,
cron writes some additional debugging information to system log during its work. Available debugging flags are:
sch scheduling
proc process control
pars parsing
load database loading
misc miscellaneous
test test mode - do not actually execute any commands
bit show how various bits are set (long)
ext print extended debugging information
-n Stay in the foreground and don't daemonize cron.
Daylight Saving Time and other time changes
Local time changes of less than three hours, such as those caused by the start or end of Daylight Saving Time, are handled specially. This
only applies to jobs that run at a specific time and jobs that are run with a granularity greater than one hour. Jobs that run more fre-
quently are scheduled normally.
If time has moved forward, those jobs that would have run in the interval that has been skipped will be run immediately. Conversely, if time
has moved backward, care is taken to avoid running jobs twice.
Time changes of more than 3 hours are considered to be corrections to the clock or timezone, and the new time is used immediately.
SIGNALS
On receipt of a SIGHUP, the cron daemon will close and reopen its log file. This is useful in scripts which rotate and age log files. Natu-
rally this is not relevant if cron was built to use syslog(3).
FILES
/var/cron/tabs cron spool directory
/etc/crontab system crontab file
/etc/cron.d/ system crontab directory
/var/log/cron log file for cron events
SEE ALSO
crontab(1), crontab(5)
AUTHORS
Paul Vixie <vixie@isc.org>
BSD
October 12, 2011 BSD