05-29-2010
Which OS is it? Is it the crontab entry of root user? How do you exactly call that script when you run it manually?
This is a plain guess, but maybe there should be a whitespace between the minus sign and oracle
10 More Discussions You Might Find Interesting
1. 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
2. Shell Programming and Scripting
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)
Discussion started by: hkapil
1 Replies
3. 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
4. UNIX for Dummies Questions & Answers
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)
Discussion started by: novice633
1 Replies
5. 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
6. UNIX for Dummies Questions & Answers
I have created a cron job for the vtiger workflow to execute the shell file named com_vtiger_workflow.sh to run the workflow.
I've created the following line in crotab -e :
00 13 * * * /var/www/html/prashant/cron/modules/com_vtiger_workflow/com_vtiger_tiger_workflow.sh | mail -s 'Check... (2 Replies)
Discussion started by: anaigini45
2 Replies
7. Shell Programming and Scripting
Dear experts,
I have this cronjob
* */2 * * * $path/supervisor.sh The supervisor script is checking another script, which initializes the final scripts in multiple directories.
Note that the supervisor script runs without the cronjob.
In each directory, I have the following script:
... (2 Replies)
Discussion started by: TheTransporter
2 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
LEARN ABOUT FREEBSD
crontab
CRONTAB(1) BSD General Commands Manual CRONTAB(1)
NAME
crontab -- maintain crontab files for individual users (V3)
SYNOPSIS
crontab [-u user] file
crontab [-u user] { -l | -r | -e }
DESCRIPTION
The crontab utility is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in Vixie Cron. Each user
can have their own crontab, and though these are files in /var, they are not intended to be edited directly.
If the allow file exists, then you must be listed therein in order to be allowed to use this command. If the allow file does not exist but
the deny file does exist, then you must not be listed in the deny file in order to use this command. If neither of these files exists, then
depending on site-dependent configuration parameters, only the super user will be allowed to use this command, or all users will be able to
use this command. The format of these files is one username per line, with no leading or trailing whitespace. Lines of other formats will
be ignored, and so can be used for comments.
The first form of this command is used to install a new crontab from some named file or standard input if the pseudo-filename '-' is given.
The following options are available:
-u Specify the name of the user whose crontab is to be tweaked. If this option is not given, crontab examines ``your'' crontab, i.e.,
the crontab of the person executing the command. Note that su(1) can confuse crontab and that if you are running inside of su(1) you
should always use the -u option for safety's sake.
-l Display the current crontab on standard output.
-r Remove the current crontab.
-e Edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. The specified editor must edit
the file in place; any editor that unlinks the file and recreates it cannot be used. After you exit from the editor, the modified
crontab will be installed automatically.
FILES
/var/cron/allow List of users allowed to use crontab
/var/cron/deny List of users prohibited from using crontab
/var/cron/tabs Directory for personal crontab files
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
SEE ALSO
crontab(5), cron(8)
STANDARDS
The crontab command conforms to IEEE Std 1003.2 (``POSIX.2'') with the exception that the dangerous variant of calling crontab without a file
name in the first form of the command is not allowed by this implementation. The pseudo-filename '-' must be specified to read from standard
input. The new command syntax differs from previous versions of Vixie Cron, as well as from the classic SVR3 syntax.
AUTHORS
Paul Vixie <paul@vix.com>
BSD
May 13, 2010 BSD