Hi,
I have a script which I am able to run from command line. When I put this in cron, it fails and gives the following message:
ld.so.1: /d00/documentum/product/5.2.5/bin/dmbasic: fatal: libdmcl40.so: open failed: No such file or directory
The ksh script looks like this:
# Set this... (1 Reply)
Hi ,
I have an issue with cron job that i have scheduled today. The problem is that when i run this script in command prompt it work good giving me the desired results but if i schedule this to run using cron job it failes giving a "syntax error in line 11 :$"..... Can anyone look into this and... (6 Replies)
I run cron in solaris 10 zone. One cron job which syncing files to nfs mounted on container, creates after finishing another cron proccess(/usr/sbin/cron), and after 100 existing cron proccesses next cron job will not start. It's too weird for me, I'm not able to solve this problem. Theoretically... (3 Replies)
This is regarding my cron job. My cron entry
30 * * * 1-5,0 /work1/informix/sample/script1.sh
31 * * * 1-5,0 /work1/informix/sample/script2.sh
Every 30 mins script1.sh is run. (mon thru friday and sunday)
Every 30 mins script2.sh is run. (mon thru friday and sunday)
This is based on the... (3 Replies)
Hi ,
I want to run script every minute so i added .
cron entry as below usning crontab -e
looks like
*/1 * * * * sh /home/sai/http_sim/http_start.sh
but cron job is not running ?
any way to start the cron or something ?
Thanks,
Raghavendra (2 Replies)
I want to update svn code using a nightly job using cron, i have created a job in cron as,
30 17-19 * * 1-5 /home/saprab/svnUpdate.sh <branch> <svnusername> <svnpassword> >> <logfile> 2>&1
svnUpdate.sh :
===============
#!/bin/bash
branch=$1
svnuser=$2
svnpass=$3
cd ${branch}... (2 Replies)
Hi,
1)
If some job supposed to run on 1st of every month at 7 AM
In cron job when we have a blackout on the 1st ( i.e when 1st falls on a sunday ) how can we make the job run the next business day?
2) How can we run a job on 25th of every quarter 7 AM(jan,apr,jul,oct)
And if 25th... (5 Replies)
Dear Members
Seeking you help on my issue.
this script need to run on every end of month.i configured as below.
but it runs everyday.
why
0 9 28-31 * * ] && /usr/bin/bash /u01///scripts/e.sh (3 Replies)
My Friends
I want to run a script only at the end of month.but i tried below cront entry its not working. pls help
0 9 28-31 ] && /usr/bin/bash /u01/app/scripts/CX-eom.shOs Details: AIX 7.1.0.0
Please use CODE tags as required by forum rules! (5 Replies)
Discussion started by: ded325
5 Replies
LEARN ABOUT SUSE
crontab
CRONTAB(1) General Commands Manual CRONTAB(1)NAME
crontab - maintain crontab files for individual users (ISC Cron V4.1)
SYNOPSIS
crontab [-u user] file
crontab [-u user] [-l | -r | -e]
DESCRIPTION
Crontab is the program used to install, deinstall or list the tables used to drive the cron(8) daemon in ISC 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 cron.allow file exists, then you must be listed therein in order to be allowed to use this command. If the cron.allow file does not
exist but the cron.deny file does exist, then you must not be listed in the cron.deny file in order to use this command. If neither of
these files exists, only the super user will be allowed to use this command.
If the -u option is given, it specifies 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(8) can confuse crontab and that if you are running
inside of su(8) you should always use the -u option for safety's sake.
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 -l option causes the current crontab to be displayed on standard output.
The -r option causes the current crontab to be removed.
The -e option is used to edit the current crontab using the editor specified by the VISUAL or EDITOR environment variables. After you exit
from the editor, the modified crontab will be installed automatically.
SEE ALSO crontab(5), cron(8)FILES
/etc/cron.allow
/etc/cron.deny
STANDARDS
The crontab command conforms to IEEE Std1003.2-1992 (``POSIX''). This new command syntax differs from previous versions of Vixie Cron, as
well as from the classic SVR3 syntax.
DIAGNOSTICS
A fairly informative usage message appears if you run it with a bad command line.
AUTHOR
Paul Vixie <vixie@isc.org>
4th Berkeley Distribution 29 December 1993 CRONTAB(1)