06-19-2008
whenever you see this:
Quote:
.. run it thro' command line. But when I schedule a script file that has rsync command thro' cron, the job doesn't get executed.
Check ENVIRONMENT variables, first off.
Where is rsynch? /usr/local/bin, maybe. cron on your box probably runs with PATH=/usr/bin. There maybe other env variables as well. Use env or printenv in the script to dump all of env variables.
cron entry--
57 13 * * * /home/apm/cron/rsync-backup.sh 2>&1 > /home/apm/cron/log
rsync-backup.sh file--
env
rsync -avz --delete -e ssh2 /san/daily_exports/export/ test@sunny01:/san/daily_exports/export
You can change this later on.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi all,
I installed Rsync on my Solaris 8 but when I ran it, it returns
ld.so.1: ./rsync: fatal: libpopt.so.0: open failed: No such file or directory
Killed
Please help. Thanks. (3 Replies)
Discussion started by: stancwong
3 Replies
2. UNIX for Dummies Questions & Answers
Hi there:
I run rsync very well by typing:
rsync -avz /source /destination
Then I want to run it by cron. So I had a crontab file like this:
* * * * * rm file
* * * * * rsync -avz /source /destination > cron_result
(The first line is used to test whether cron is working.)
When I check... (0 Replies)
Discussion started by: Steven.surfboy
0 Replies
3. UNIX for Advanced & Expert Users
Hi,
I am running a rsync via cron job.
Its running fine and is scheduled to 9:00 AM everyday.
Sometimes it runs for more than 24 hours, such that the next days cron also fires.
Now how will the sync happen as the <sync file> that both crons have created might conflict.
Thanks (5 Replies)
Discussion started by: vibhor_agarwali
5 Replies
4. Shell Programming and Scripting
I have the following rsync script that I use for syncing MySQL files from one server to another. I run the script at 20 minutes past every second hour in cron. I want to make sure that the script completes in it's entirety before it is set to kick off again. For example, when the script starts at... (3 Replies)
Discussion started by: sunsysadm2003
3 Replies
5. UNIX for Advanced & Expert Users
Hi,
I am able to use rsync and run it thro' command line. But when I schedule a script file that has rsync command thro' cron, the job doesn't get executed. All other jobs in the cron runs fine.
cron entry--
57 13 * * * /home/apm/cron/rsync-backup.sh
rsync-backup.sh file--
rsync -avz... (1 Reply)
Discussion started by: sm23328
1 Replies
6. UNIX for Dummies Questions & Answers
Hi,
I've created a cron job for a script with a rsync command in it. The script is named pull.sh and contains the following line :
What it is supposed to do is pull backup files from the production server of my company to my local server. It should also generate the log file (output.log)... (1 Reply)
Discussion started by: anaigini45
1 Replies
7. Red Hat
hi all, i have scripts executable in manully, but not working in cron. any ideas? thanks a lot?
* * * * * /home/dir/dir/file.sh
#! /bin/sh
alarmPath="/home/dir/monitoringAlarm"
alarmDateTime="$(date +%Y%m%d) $(date +%H%M%S)"
tomcatPID=`pidof /usr/local/jdk1.6.0_13/bin/java`
echo "tomcat... (1 Reply)
Discussion started by: maxlee24
1 Replies
8. Shell Programming and Scripting
hi all, i have scripts executable in manully, but not working in cron. any ideas? thanks a lot?
* * * * * /home/dir/dir/file.sh
#! /bin/sh
alarmPath="/home/dir/monitoringAlarm"
alarmDateTime="$(date +%Y%m%d) $(date +%H%M%S)"
tomcatPID=`pidof /usr/local/jdk1.6.0_13/bin/java`
echo "tomcat... (3 Replies)
Discussion started by: maxlee24
3 Replies
9. UNIX and Linux Applications
So I have this rsync script I wrote to grab some sql files and import them to a database. I left in the mysql stuff just give context to the situation. The real problem is with my rsync code.
script.sh (chmod 744)
#!/bin/sh
rsync -av --rsh="sshpass -p'PASSWORD' ssh -l'USERNAME'"... (3 Replies)
Discussion started by: noPermissions
3 Replies
10. Shell Programming and Scripting
Help. My script is working fine when executed manually but the cron seems not to catch up the command when registered.
The script is as follow:
#!/bin/sh
for file in file_1.txt file_2.txt file_3.txt
do
awk '{ print "0" }' $file > tmp.tmp
mv tmp.tmp $file
done
And the cron... (2 Replies)
Discussion started by: jasperux
2 Replies
LEARN ABOUT X11R4
queuedefs
queuedefs(4) File Formats queuedefs(4)
NAME
queuedefs - queue description file for at, batch, and cron
SYNOPSIS
/etc/cron.d/queuedefs
DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue.
The format of the lines are as follows:
q.[njobj][nicen][nwaitw]
The fields in this line are:
q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see
at(1)); c is the default queue for jobs run from a crontab(1) file.
njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first
njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100.
nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2.
nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's
queue, or because the system-wide limit of jobs executing has been reached. The default value is 60.
Lines beginning with # are comments, and are ignored.
EXAMPLES
Example 1: A sample file.
#
#
a.4j1n
b.2j2n90w
This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value
of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying
again to run it.
The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job
cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can
have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs
are running cron will wait 60 seconds before trying again to run it.
FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron.
SEE ALSO
at(1), crontab(1), nice(1), cron(1M)
SunOS 5.10 1 Mar 1994 queuedefs(4)