12-19-2012
Crontab issue !
Guy's
I'm facing problem with crontabe in Solaris10
and cron in crontab -e is not running but when I check /var/cron/log
I found all the process running .. !! strange thing !!
please your advice ...
10 More Discussions You Might Find Interesting
1. HP-UX
Dear Folks,
i am new to hp-ux, i have a problem scheduling the crontab,
The script is working fine at command prompt, but not working at cron, please find a solution for it ,
here are the logs and my schedule at cron:
log after restarting crontab /var/adm/cron/log
! *** cron started *** ... (11 Replies)
Discussion started by: vaddi
11 Replies
2. UNIX for Advanced & Expert Users
I am adding a piece of code which adds entry in crontab ((in brown color))
\crontab -l > $tmpfile
echo "Removing the cleanProcess entry if it already existed.."
grep -v "cleanProcess.sh" $tmpfile > $newtmpfile
lcnt=`grep -c "cleanProcess.sh" $tmpfile`
echo... (4 Replies)
Discussion started by: crackthehit007
4 Replies
3. Shell Programming and Scripting
Helo .
I have 2.6.13-1.1526_FC4smp here.
I am trying to make crontab execute my simple shell script, but noting happens.
here is how i am testing this :
$ pwd
/home/oracle
$ ls -l two*
ls: two*: No such file or directory
$
$ crontab -e
crontab: installing new crontab
$
$ crontab... (7 Replies)
Discussion started by: tonijel
7 Replies
4. Shell Programming and Scripting
I have a ksh script which will connect to a database and executes some sql scripts. If i run the ksh script it is working fine. But if i schedule it to run at a perticular time using cron the sql script is not running. The scriptl initially creates a spool file for sql script and then connects and... (12 Replies)
Discussion started by: Sriranga
12 Replies
5. UNIX for Advanced & Expert Users
We have configured a script to be run at specific time using crontab.
# crontab -l
15 11 * * * VM_Count_V4.shas per the crontab entry script should run every day 11.15 a.m
Every time when the script is executed i get a mail but when i run it using crontab it doesn't send any mail.
However... (1 Reply)
Discussion started by: pinga123
1 Replies
6. AIX
Hi all,
I'm having a problem with a crontab entry execution for a non root user.
AIX version 5.3
user@host ~ $ oslevel -r
5300-10
cron status
user@host ~ $ ps -ef | grep cron
root 377044 1 0 Oct 27 - 0:22 /usr/sbin/cron
cron entry for user
user@host ~ $... (3 Replies)
Discussion started by: h@foorsa.biz
3 Replies
7. UNIX for Dummies Questions & Answers
Hi,
I have a cronjob but it is not getting executed.Is there any ways to check whether crontab is working.I have put crontab -l and checked.It got listed.But it is not working.
My Crontab is,
* * * * * /ldesk/home/abc/source/compare.sh >/dev/null 2>&1 (1 Reply)
Discussion started by: gayisada
1 Replies
8. Shell Programming and Scripting
hi,
i have schduled a job through crontab, but it is not getting executed.
bash-3.2$ crontab -l
# Monthly Download (mm hh DD MM format)
35 05 01 04 * /home/ftpsrp/srpftp1/download/ofrdb/scripts/load_ofrdb.sh crr.sh
here is the permission of the .sh files
-rwxr--r-- 1 ftpsrp srp ... (7 Replies)
Discussion started by: lovelysethii
7 Replies
9. UNIX for Advanced & Expert Users
My colleague who was a sysadmin , has created a cron job script which collects logs and process them.
The script works perfectly as per the defined time set by him.
it works when we keep the timing as 55 05 * * * , whereas if we try to prepone the cron task is not getting executed.
Where... (10 Replies)
Discussion started by: aravindj80
10 Replies
10. UNIX for Dummies Questions & Answers
Hello,
I have a bash script that finds files older than 31 days and deletes them. I have this file loading into crontab to run everyday. It ran fine the first time i loaded it in, but now when I try to run it manually (bash file.sh) I get errors.
Here is the script
TIME=" -maxdepth 1... (6 Replies)
Discussion started by: jrymer
6 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