I can build the latest rdiff on a Sun system without
a problem (except for lots varargs warnings in building librsync),
but it will not run - no matter how I specify -R -L linker
flags or specifying LD_LIBRARY_PATH.
I have built this on other Sun and Linux systems without a
Hey, folks.
I sent this message to Ben a few weeks ago, but maybe it should be
here instead. I hope it proves useful.
I've started using rdiff-backup to backup to a computer that isn't
always available. I rigged up a complicated system with a wrapper
script and anacron, so that it always tries
Okay I need some help here to figure out this traceback so I can get
rdiff-backup running properly. I am trying to back up a FreeBSD-4.11 (client)
to a Fedora Core 4 machine (server).
installation of all rdiff-backup software was fine. I've been using
rdiff-backup for some time now and this
Hi
I want that rdiff-backup connects direcly to a remote server using TCP
so since this is not supported on client side I did a small patch(below)
On remote side just use inetd/xinetd/whatever like this:
#cat /etc/xinetd.d/rdiff-backup
service rdiff-backup
{
socket_type = stream
Here is an idea.
What if there were a way to trigger an rdiff-backup of a single file
after a samba update connection finished. I'd noticed some time ago
that Samba can execute commands before and after a file is served.
Wouldn't it be neat to update the increments after every save?
--
Joe
On Wed, 1 Mar 2006, Brian C. Hill wrote:
ImportError: ld.so.1: /usr/pkg/python/bin/rdiff-backup: fatal:
librsync.so.1: open failed: No such file or directory
-
What am I doing wrong? Is an old Python installation (this
I found the problem - a weird one.
At some point, someone had run crle with several -i dir options,
which I am guessing causes crle to load all of the libraries (not lib
dirs) found in the specified dirs in ld.so.cache. That configuration
seems to preempt ld from loading any 'new'
