[PATCH] Unsnarl missing_below/dry_run logic.

The generator can skip a directory's contents altogether due to --ignore-non-existing, a daemon exclude, or a mkdir failure. On a --dry-run, the generator can also note the missingness of a directory while still scanning its contents. These two scenarios were conflated using a single set of missi

RE: static compile of rsync

paul I added the "-static" to my CC environment: bash> export CC=-static bash> ./configure; make here are my last few output lines from make: gcc -std=gnu99 -I. -I. -static -DHAVE_CONFIG_H -Wall -W -c zlib/compress.c -o zlib/compress.o gcc -std=gnu99 -I. -I. -static -DHAVE_CONFIG_H -Wall -W -

Re: Incremental file updates over a network, NFS?

For internal stuff, there is a hosts allow/deny feature built right into the rsync configuration file to allow rsync storageplaces access to only from a particular IP address. For general Internet stuff, I too did not want interactive logins, thus preventing the ssh key method of using ssh to e

Re: static compile of rsync

* Message by -Paul Slootman- from Tue 2008-03-18: > On Tue 18 Mar 2008, Lasse Kliemann wrote: > > * Message by -Paul Slootman- from Tue 2008-03-18: > > > > > Be aware that at least when using glibc, a number of things are always > > > dynamic, e.g the nsswitch stuff (for host lookups etc.) > > >

Re: --detect-moved patch and --link-dest

On Fri, 2008-03-07 at 14:20 +0100, Matt wrote: > I am using --link-dest for my rotating backups. Noticing the > "--detect-renamed-lax" patch to rsync 3.0.0. I was hoping to make use > of the --detect-moved. Unfortunately, "--detect-moved" does not seem > to recognize the --linkdest option.

Re: static compile of rsync

On Tue 18 Mar 2008, Lasse Kliemann wrote: > * Message by -Paul Slootman- from Tue 2008-03-18: > > > Be aware that at least when using glibc, a number of things are always > > dynamic, e.g the nsswitch stuff (for host lookups etc.) > > If the targets are linux systems, then the safest way is to bu

Re: crypting remote data

On Mon, 2008-03-10 at 22:55 +0100, david reinares wrote: > when I'm restoring the crypted data after a while rsync shows > rsync: Failed to close: Bad file descriptor (9) > rsync: Failed dup/close: Bad file descriptor (9) > rsync error: error in IPC code (code 14) at pipe.c(208) [receiver=3.0.0] >

Re: Do we need excluded_below?

On Tue, 2008-03-18 at 11:51 -0700, Wayne Davison wrote: > The latest version in the git repository has thwarted my attempts at > receiving or sending files inside an excluded directory. With "exclude = /secret" in the configuration file, I can still pull the contents of a daemon-excluded directory

Re: static compile of rsync

* Message by -Paul Slootman- from Tue 2008-03-18: > Be aware that at least when using glibc, a number of things are always > dynamic, e.g the nsswitch stuff (for host lookups etc.) > If the targets are linux systems, then the safest way is to build > appropriate packages... rsync can be linked s

Re: Do we need excluded_below?

On Sun, Mar 09, 2008 at 08:24:53PM -0400, Matt McCutchen wrote: > I propose removing excluded_below. This would only make daemons that > are already insecure more glaringly so, and it would have the benefits > of simplifying the code and making any weaknesses in the daemon-exclude > checking more

Re: static compile of rsync

On Tue 18 Mar 2008, Lopez David E wrote: > I've looked at the last 6 months on the list and did > not find any reference on how to static compile of > rsync. I looked at the ./configure --help with no luck. > > I'm on solaris 2.8 using gcc 4.1.1. when I run thru the > process (./configure; make;

static compile of rsync

I've looked at the last 6 months on the list and did not find any reference on how to static compile of rsync. I looked at the ./configure --help with no luck. I'm on solaris 2.8 using gcc 4.1.1. when I run thru the process (./configure; make; make install) and run ldd rsync, I get a list of 10 o

AW: rsync Windows UNC

Here a detailed list what I've done: - I installed the cygwin standard distribution, - uninstalled the cwrsync - then created the needed mount points: Mkdir /mnt Mkdir /mnt/Sharename - added them into registry [HKEY_LOCAL_MACHINE\SOFTWARE\Cygnus Solutions\Cygwin\mounts v2] - installed rsync, cygr

Re: Suggestions for basic rsync configuration

On Tue, 2008-03-18 at 03:38 -0700, Peter Heiss wrote: > So now I have tried the daemon again, and got a password prompt, which is > better. I edited the "host allow = *" so that it would allow all hosts. But > I tried at first adding the IP Address of my local router, and it didnt > work. How can I

Re: rsync Windows UNC

On Tue, 2008-03-18 at 07:55 +0100, Kalb Stefan wrote: > after some pain it works now. Great! How did you fix the problem (for the benefit of users having issues with UNC paths on Cygwin in the future)? Matt -- To unsubscribe or change options: https://lists.samba.org/mailman/listinfo/rsync Bef

AW: AW: rsync Windows UNC

Matt, after some pain it works now. Many thanks for your help. > -Ursprüngliche Nachricht- > Von: Matt McCutchen [mailto:[EMAIL PROTECTED] > Gesendet: Montag, 17. März 2008 19:18 > An: Kalb Stefan > Cc: rsync > Betreff: Re: AW: rsync Windows UNC > > Stefan, > > Please keep this on th

Re: Suggestions for basic rsync configuration

Matt McCutchen-7 wrote: > >> hosts allow = trusted.hosts > > BTW, the "hosts allow" field needs to contain the actual list of trusted > hosts, not the name of a file holding the list. > So now I have tried the daemon again, and got a password prompt, which is better. I edited the "host allow