If anybody else was wondering, I found the problem - there's a routing
issue in ip.att.net which is apparently preventing most if not all of
the entire Southeastern USA from accessing the network cygwin.com and
sources.redhat.com are on.
Anything from the local RoadRunner, xpedius in FL, Nuvox in S
http://livere.biz/OE017/?affiliate_id=233642&campaign_id=601
--
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.catb.org/~esr/faqs/smart-questions.html
Has anybody else noticed cygwin.com and sources.redhat.com being down?
The machine that answers to those addresses (and sourceware.org) is
refusing HTTP connections, and has been for at least 48 hours now.
Anybody here know anything about it? I haven't been able to find out
diddly-squat about
On Fri, May 07, 2004 at 06:54:32PM -0400, Chris Shoemaker wrote:
> /* if (!write_batch) */
>send_exclude_list(f_out);
>
> at main.c:641.
>
> This seems to work better, because things get further.
I looked at the receiving side, and I think that code should probably
be "if (!read_batch)" inst
On Sun, May 09, 2004 at 03:35:47AM -0700, Robert Helmer wrote:
> If there is an error writing to the remote file due to a "permission
> denied" error, rsync 2.6.1's client exits with an error code of 23, and
> an informative error message.
... and no error message logged in the server's log file.
On Sun, May 09, 2004 at 11:21:12AM +0200, Pawe? Go?aszewski wrote:
> Is there any solution?
The current solution is to run rsync using either the -6 or the -4
option (either should work, but -4 will limit rsync to listening for
IPv4 connections). I believe that this problem only affects older
ver
On Sun, 9 May 2004 3:45am, Robert Helmer wrote:
(in rsync-2.6.0 source directory)
Sorry, small correction to my previous email - above should state
"rsync-2.6.2" not "rsync-2.6.0" .. I did not test w/ the latter. The
following is the valid output for 2.6.2 in my tests.
$ ./configure
$ make
$
Hello,
Noticed this (bug?) while testing out rsync. For a little background, I
need to push files real-time to some front-end servers, and I am
thinking of switching from some custom shell scripts that do this job
to rsync. I am thinking of running rsync as a daemon on the front-end
servers, and
After upgrade from previous version I can't run rsync.
2004/05/09 10:40:54 [18630] rsyncd version 2.6.2 starting, listening on port 873
2004/05/09 10:40:54 [18630] rsync error: error in socket IO (code 10) at socket.c(466)
strace shows that there is problem with listen()
I've found patch on thi
