Re: SIGUSR1 or SIGINT error

2002-02-07 Thread Dave Dykstra
On Wed, Feb 06, 2002 at 04:29:49PM -0700, Eric Whiting wrote: Dave, I tried the snapshot... I get an error (after a ./configure;make). gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c main.c -o main.o main.c: In function `do_cmd': main.c:184: `RSYNC_RSH' undeclared (first use in this

Re: SIGUSR1 or SIGINT error

2002-02-07 Thread tim . conway
Currently 2.5.1pre3. I haven't tested that problem lately, though. I'll get the newest up and try a full sync. It's worth a try. I'll feel really stupid, though, if i've put all this work into newsync (perl driving find|diff|tar|lzop) and it's fixed in rsync. I think our case will

Re: SIGUSR1 or SIGINT error

2002-02-07 Thread David Birnbaum
I'm running 2.5.2. However, we had the same type of problem with 2.4.6, which is what we were running before. If I had to guess, I would say that we're seeing this error a little more often in 2.5.2. David. - On Thu, 7 Feb 2002 [EMAIL PROTECTED] wrote: Currently 2.5.1pre3. I haven't

2.5.3pre compile warnings

2002-02-07 Thread Eric Whiting
Dave, I just got the latest snapshot and compiled. I'll run 2.5.3pre on a few boxes and see how it acts.. Is --compress safe again? I know not all the warnings are of concern, but I thought I'd bounce my warning output to you. gcc version 2.95.3 20010315 (SuSE) The zlib/ warnings about missing

Re: SIGUSR1 or SIGINT error

2002-02-07 Thread Dave Dykstra
The fix that went into 2.5.0 was for timeouts that were happening even when --timeout=0 (the default). Can any of you say for sure that it makes a difference with a new version when you go from --timeout=0 to a very large timeout? I want to see if Tim's experience with timeouts defaulting to

Re: configure --with-rsh=CMD and default blocking-IO support

2002-02-07 Thread Dave Dykstra
On Wed, Feb 06, 2002 at 02:56:38PM -0800, Wayne Davison wrote: On Wed, 6 Feb 2002, Dave Dykstra wrote: Of the proposed alternatives, I like this latter the best, changing --non-blocking-io to --no-blocking-io. Cool. I like that one as well. Here's an implementation. This patch adds

Re: configure --with-rsh=CMD and default blocking-IO support

2002-02-07 Thread Dave Dykstra
On Wed, Feb 06, 2002 at 06:25:05PM -0800, Wayne Davison wrote: On Thu, 7 Feb 2002, Martin Pool wrote: A general-purpose RSYNC_OPTS variable would be more tasteful. I think popt makes supporting this fairly straightforward. That's a nice idea. One area we'll want to be careful of is how

change for receiver.c

2002-02-07 Thread Jim Ogilvie
Here's a suggested change for receiver.c in version 2.5.2. It works in aix 4.3.3. *** receiver.c.org --- receiver.c *** *** 427 ! rprintf(FERROR,mkstemp %s failed\n,fnametmp); --- 427 ! rprintf(FERROR,mkstemp %s failed: %s\n,template,strerror(errno)); (Sorry,

Deleting files from source after a successful rsync !

2002-02-07 Thread Kapoor, Nishikant X
I have a few clients who prepare some reports and put it in their outgoing/ directory for me to pick up every morning. Is there a way to delete those files from their outgoing/ after I fetch them ? Thanks Nishi

Re: Deleting files from source after a successful rsync !

2002-02-07 Thread Wayne Davison
On Thu, 7 Feb 2002, Kapoor, Nishikant X wrote: I have a few clients who prepare some reports and put it in their outgoing/ directory for me to pick up every morning. Is there a way to delete those files from their outgoing/ after I fetch them ? You can use my --move-files patch for this,