Dear Mr. Samir,
We are using RedHat 7.2. We are getting same error as reported by you
some time back (given below).
Did you get any solution?
Regards
C Jagadish
Your original message:
==
I m running RedHat 9 Linux and I have the rsync-2.5.5-4 package.
When I m trying t
That patch works perfectly. I ran my test about 15
times and both processes on the server died just like
they're supposed to. Thanks.
On Wed, Mar 15, 2006 at 12:32:57PM -0800, Wayne Davison wrote:
> On Wed, Mar 15, 2006 at 11:41:26AM -0600, Steve Sether wrote:
> > I've gotten around to testing t
I have been using rsync 2.6.6, to do an across the network sync on a quiet
system in a Solaris 8 environment. Rsync is compiled from src on the
sunfreeware gcc compiler, and has worked excellently in this capacity. We
are now wanting to attempt to do a similar thing more often in a 'live'
env
Rsync does not seem to feature include directives as samba in order to
manage the config file in several seperate ones. I would like to know if
I am right and in that case, I suggest it would be an interesting feature.
Separating the configuration of the server itself from the ressources
it off
https://bugzilla.samba.org/show_bug.cgi?id=3609
Summary: Bad behavior when there are IO errors on reading.
Product: rsync
Version: 2.6.7
Platform: x86
OS/Version: Linux
Status: NEW
Severity: major
Priority: P3
On Wed, Mar 15, 2006 at 11:41:26AM -0600, Steve Sether wrote:
> I've gotten around to testing the generator hang bug using stunnel
> under 2.6.7, and I still occasionally get the same problem.
I believe that the following patch should fix the problem for you.
Please give it a try and let me know h
On Wed 15 Mar 2006, Simon Margulies wrote:
> I'm trying to update my rsync on os x 10.4.5.
>
> downloaded the latest rsync-2.6.7.tar.gz
> as described in the configure --help I started ./configure and the
> output tells me that all works out fine.
>
> then running rsync (in /usr/local/bin) in
I'm trying to update my rsync on os x 10.4.5.
downloaded the latest rsync-2.6.7.tar.gz
as described in the configure --help I started ./configure and the
output tells me that all works out fine.
then running rsync (in /usr/local/bin) in bash the output still tells
me, it would be: rsync ve
On Wed, Mar 15, 2006 at 11:41:26AM -0600, Steve Sether wrote:
> Run 2 hangs indefinately.
Thanks for the extra info. It shows that the generator is trying to
finish writing out a buffer of data before re-checking for messages from
the receiver (this is how it currently avoids intermingling forwar
I've gotten around to testing the generator hang bug using stunnel
under 2.6.7, and I still occasionally get the same problem. It
seems to be around 50% of the time. Here's some strace output from the
generator and receiver from two runs, one where the generator exits
properly, and one where it d
On Wed, Mar 15, 2006 at 09:21:16AM +0100, Liesinger Horst wrote:
> Does option --include not outomaticaly exclude not matching files ?
No, it does not. All files are included by default, so if you don't
exclude anything, no changes will be made to rsync's actions. Adding an
--exclude='*' option
https://bugzilla.samba.org/show_bug.cgi?id=3392
--- Comment #11 from [EMAIL PROTECTED] 2006-03-15 10:27 MST ---
I appreciate than in your specific circumstance that an enhance behavior of
--fuzzy would be useful. My testing of the --fuzzy option has also included
large transfers with
Hello,
I was trying to syncronize two directories with --include="*800*" or "800*"
or "/800*", but I always et the same file list. Does option --include not
outomaticaly exclude not matching files ?
/usr/local/bin/rsync -n --include="800*" --rsh=remsh
--rsync-path=/usr/local/bin/rsync -rzpogctS -
13 matches
Mail list logo
