Full path looks better than without. Make sure that you have the same environment like when you start it on the command line.
... looks to me as if there is still some variable that contains a path to some libraries is not set when being executed via cron.
Check the original environment of that user with the command env and set and do same with your script being fired off via cron and compare if there is some obvious looking variable is not set.
Make sure that this script/cronjob sources the .profile and any other needed environment files.
Last edited by zaxxon; 10-28-2009 at 08:51 AM..
Reason: added info
Hi,
I made this script for TRU Unix 5.1 OS based Node.
When the script was run manually all the commands were running properly. But when it was run from Crontab, one command is not running.
This command is not running when the script is running from Crontab:
#... (2 Replies)
I am facing a strange issue while running a script(eg A) from the crontab entry
the script calls one more script(eg B) within it
now when i run the script A manually(with nohup) it also executes the script B (embedded inside it) as expected.
but when i run the script A from the crontab entry... (7 Replies)
Hi,
I'm trying the backup a few information commands of my Check Point FW (it's on a SPLAT linux machine). This is the script I wrote:
#!/bin/bash
cd /var/tmp/
file1=netstat_`/bin/date +%d%m%y`.txt
file2=ifconfig_`/bin/date +%d%m%y`.txt
file3=cpstatos_`/bin/date +%d%m%y`.txt... (2 Replies)
Hi, I posted this in the Solaris forum but I think this one would be more appropriate.
I created a script starting with the following lines:
#!/usr/bin/ksh
flag=n
export flag
typeset -i quant=0
(...)
When running it I'm getting the following 2 errors:
/tmp/tstscript/testfail.ksh:... (9 Replies)
Hi,
I have created the below script,
set -x
# Set the Path of Environment file
ENV_FILE_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/bin
LOG_DIR=/opt/app/p1trp1c1/sybase/ecdwqdm/xrbid/QDM_Prod/log
export ENV_FILE_DIR
export LOG_DIR
# Set Audit Environment
. ${ENV_FILE_DIR}/QDM.env... (8 Replies)
Hi All,
I am having the below script to be run from crontab, it it doesnt run.
1 * * * * /home/cobr_ext/test.sh > /home/cobr_ext/temp.txt
when i run i manally it runs without any issues.
Could please help me as to why doesnt it run the script.:( (7 Replies)
I am facing an issue where sometimes crontab is running script with some delay.
Below is the stmt in script and it is the only stmt in script.
echo "running at `date` " >> CRONCHECK.log
Below is the cron entry.
0 11 * * * CRONCHECK.sh
Below is the time of run each day.
running at Fri... (8 Replies)
hi All,
i have implemented Rsync in my source and destination server. while running through command prompt it is working fine:
ksh rsync_bravo_db.ksh usa0300uz1252.apps.mc.xerox.com /uv1402/u207/home/bravodba/bin/rsync-3.0.9/config/mrsx_rsync.cfg
but later on i created a another ksh and... (4 Replies)
Hi guys!
I created a backup script that works fine when I run manually, but when I put a crontab job to execute it the result are not the expected. (not a time problem).
Here is my script:
bash-3.00# cat /bk_tool/backup2.sh
#!/usr/bin/csh
clear
set DIR_HOST='SCP08'
... (3 Replies)
Hi!
I'm using a RaspberryPi with standard Raspbian.
Currently I'm working on some sort of weather station.
For now I have three python scripts - one which is updating txt files for website - update1m.py ( it will not be necessary in few next days so I'll delete it) , second one for updating... (4 Replies)
Discussion started by: bartocham
4 Replies
LEARN ABOUT CENTOS
yum-cron
yum-cron(8)yum-cron(8)NAME
yum-cron - an interface to convieniently call yum from cron
SYNOPSIS
yum-cron [config-file]
DESCRIPTION
yum-cron is an alternate interface to yum that is optimised to be convenient to call from cron. It provides methods to keep repository
metadata up to date, and to check for, download, and apply updates. Rather than accepting many different command line arguments, the dif-
ferent functions of yum-cron can be accessed through config files.
config-file is used to optionally specify the path to the configuration file to use. If it is not given, the default configuration file
will be used. It is useful to be able to specify different configuration files for different use cases. For example, one configuration
file might be set to update the repository metadata, and a line could be added to the crontab to run yum-cron frequently using this file.
Then, another configuration file might be set to install updates, and yum-cron could be run from cron using this file just once each day.
FILES
/etc/yum/yum-cron.conf
/etc/yum/yum-cron-hourly.conf
SEE ALSO
yum (8)
AUTHORS
See the Authors file included with this program.
BUGS
There of course aren't any bugs, but if you find any, you should email
the mailing list, yum@lists.baseurl.org, or consult bugzilla.
Nick Jacekyum-cron(8)