06-30-2009
Crontab error
Hi,
I have following crontab en my user:
*/5 * * * * command
it's don't run every Five minutes, why?
Anyone know what is it happend?
Thankyou.
10 More Discussions You Might Find Interesting
1. Linux
Hi guys,
OS Red Hat Enterprise 4. Problem:
By oravwp user I can't use crontab -e, report the error:
cron/oravwp: Permission denied
I have experience in HP-UX and Sun Solaris, and the problem seems not to be easy or I going old with all of this :). The file /etc/cron.deny exist, it's empty,... (5 Replies)
Discussion started by: uadm26
5 Replies
2. Shell Programming and Scripting
Yesterday i installed a new cron on solaris box. After a few minutes after loading the cron, i got the following error.
Your "crontab" on machine_name
!
unexpected end of line
This entry has been ignored.
Do any of you have any idea about this error ? (12 Replies)
Discussion started by: dhanamurthy
12 Replies
3. UNIX for Dummies Questions & Answers
So I'm trying to set up a simple cron job to copy the contents of a folder to my local machine. When it's ran the following output is produced:
sh: syntax error at line 1: `(' unexpected
Here's line 1:
scp -r user@host:/cygdrive/c/logfolder1/ /log_files/$(date +%m_%d_%Y) (2 Replies)
Discussion started by: kclerks11
2 Replies
4. UNIX for Advanced & Expert Users
when i say
$crontab z
it says ==>
"z":6: bad minute
"z":6: bad minute
errors in crontab file, can't install.
any clue why its happening? (1 Reply)
Discussion started by: crackthehit007
1 Replies
5. Shell Programming and Scripting
I have a script which is called in a crontab. The script calls for 2 args when ran on the command line
The crontab line:
05 0-23 * * 0-6 /path/name %arg1 %arg1
I get the following output
Your "cron" job on server
/path/name
produced the following output:
Must be attached to... (4 Replies)
Discussion started by: Pablo_beezo
4 Replies
6. UNIX for Dummies Questions & Answers
I am trying to create a crontab job for my Oracle logon. I added oracle to the cron.allow file but when I try the crontab -e I get:
Xlib:connection to 0:0 refused by server
Xlib:Client is not authorized to connect to server
Error:Cannot open display "0:0"
crontab temporary file empty
when... (3 Replies)
Discussion started by: dman110168
3 Replies
7. UNIX for Dummies Questions & Answers
Hi all,
I wrote small script for Solaris and when I am running it through command prompt its ok, but when I trying to run it using crontab, i am getting error like:
ld.so.1: dbloader: fatal: libACE.so: open failed: No such file or directory
/tmp/file.sh: line 5: 8304 Killed ... (4 Replies)
Discussion started by: nypreH
4 Replies
8. UNIX for Dummies Questions & Answers
Hi Guys,
I need to edit the crontab on one of my unix systems. When I execute crontab -e, nothing happens, then I get an error '666' and can't type anything else at the cli.
I tried resizing the window, but still got the same error. I'm using the run user and I've checked the permissions on... (0 Replies)
Discussion started by: bbbngowc
0 Replies
9. Shell Programming and Scripting
Hi All,
I have created crontab using following steps-
1) crontab -e
(edited the file with) 0 10 * * 1-5 /home/user01/exercise/cron.sh
2) then saved this file with :wq
3) cron.sh contains the code-
#!/bin/bash
DAY=`date +%a`
mkdir abc_${DAY}
4) done the execut permision... (3 Replies)
Discussion started by: pspriyanka
3 Replies
10. Solaris
Hi,
I run crontab -l ,then i got error message like "crontab: can't open your crontab file."
I checked for entry in cron.allow and entry was present, nothing in cron.deny.
Note: It is working for another user.
Can someone suggest? (2 Replies)
Discussion started by: Mani_apr08
2 Replies
CRON(8) System Manager's Manual CRON(8)
NAME
cron - daemon to execute scheduled commands (ISC Cron V4.1)
SYNOPSIS
cron [-l load_avg] [-n]
DESCRIPTION
Cron should be started from /etc/rc or /etc/rc.local. It will return immediately, so you don't need to start it with '&'. The -n option
changes this default behavior causing it to run in the foreground. This can be useful when starting it out of init.
Cron searches /var/spool/cron for crontab files which are named after accounts in /etc/passwd; crontabs found are loaded into memory. Cron
also searches for /etc/crontab and the files in the /etc/cron.d directory, which are in a different format (see crontab(5)). 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 execut-
ing 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).
Additionally, cron checks each minute to see if its spool directory's modtime (or the modtime on /etc/crontab) 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 whenever a crontab
file is modified. Note that the Crontab(1) command updates the modtime of the spool directory whenever it changes a crontab.
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.
PAM Access Control
On SUSE LINUX systems, crond now supports access control with PAM - see pam(8). A PAM configuration file for crond is installed in
/etc/pam.d/crond . crond loads the PAM environment from the pam_env module, but these can be overriden by settings in the crontab file.
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.
Naturally this is not relevant if cron was built to use syslog(3).
CAVEATS
In this version of cron, /etc/crontab must not be writable by any user other than root. No crontab files may be links, or linked to by any
other file. No crontab files may be executable, or be writable by any user other than their owner.
SEE ALSO
crontab(1), crontab(5), pam(8)
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 10 January 1996" CRON(8)