As I alluded to in an earlier email on the subject of excludes, I had
the idea of allowing a merge idiom (think "#include" in C) inside
rsync's current exclude/include system. The idea is simple -- use the
prefix ". " (dot space) in front of a filename, and that file will be
incorporated into the
Hopefully the email to the announce list will show up soon. Until then,
you can get a jump on the rest by checking out the rsync home page to
read the announcement:
http://rsync.samba.org/
It includes a security note about a fix that affects read/write daemons
that are not using chroot. If
On Thu, Apr 22, 2004 at 04:20:07PM -0400, John Taylor wrote:
> Upon a suggestion to improve the --timelimit patch, I have also added
> a --stopat option.
CVS now has an updated time-limit.diff patch in which I simplified the
code quite a bit and tweaked the options a bit:
[EMAIL PROTECTED]:MM
Hi all,
I'm wanting to make weekly backups of host qin to host elijah. I set a
crontab to run a script that effectually executes this rsync command:
rsync -ave ssh --exclude-from=excludes.txt --delete /
elijah:/home/backup/qin
host qin is running gentoo linux with rsync version 2.5.6.
host eli
does anyone use rsync as a backup server?
i got the following error msg.
please help
building file list ...
link_stat /mnt/nw/DATA2/POP/APPS : Input/Output error
done
delta transmission enabled
total: matches=0 tag_hits=0 false_alarms=0 data=0
wrote 17 bytes read 20 bytes 2.74 bytes/sec
total siz
In my case rsync -e rsh 66.123.34.123:/etc/services just works fine. I understand that
now i dont have to use rsync-path. My whole purpose of using rsync is to backup a
directory from source machine to destination machine. In order to accomplish that i
gave the command at the source machine:
r
I gave the example, and understood that you'd used it. If instead of "
rsync -e rsh --rsync-path=/usr/local/bin/rsync 66.123.34.123:/etc/services
", you used "rsync -e rsh 66.123.34.123:/etc/services" and it worked, then
you don't need the --rsync-path= option. If however, the second example
ab
Tim Conway <[EMAIL PROTECTED]> wrote:
assuming you replaced "hostwithrsync" with "66.123.34.123", you're in.
Yes, i replaced it with the ip address.
I have a question about rsync-path option. The command I am giving at the source
machine is:
rsync -aznrbe rsh /sourcepath 66.123.34.123:/desti
assuming you replaced "hostwithrsync" with "66.123.34.123", you're in.
It's fine that your /etc/services is a symlink... the important thing is
that you can see it with rsync over rsh.
Use the rsync-path option, and enjoy the tool.
Tim Conway
Unix System Administration
Contractor - IBM Global Se
Hello Tim,
Sorry for the late response. I was out of town for weekend.
Ok, first I tried
rsync -e rsh --rsync-path=/usr/local/bin/rsync hostwithrsync:/etc/services
I got the following the output:
-rw-r--r-- 73490 2003/10/27 09.26.50 services
Jim: first - glad to see you're able to reach the group again.
Second: In later messages, he'd found and fixed true rsh - to where "rsh
remotehost which rsync" returned "/usr/local/bin/rsync", and still got the
timeout on actual rsyncs.
I sent an enormous number of possible outputs he could get
> The backtrace you cite looks to be impossible (nested calls to
> send_file_list() can't happen), so I assume that the list
> is not valid
> for some reason. I haven't seen such a hang as you
> describe. Have you
> delved into this any further?
Well what I did after my last post was recompili
12 matches
Mail list logo
