On Mon, Aug 18, 2003 at 01:59:37PM -0700, jw schultz wrote:
> On Mon, Aug 18, 2003 at 01:41:51PM -0700, David Norwood wrote:
> > > > Okay, with this patch I now get error messages, but it still creates
> > null
> > > > filled output files. I guess that is what you meant by "the behavior is
> > the
Committed.
On Mon, Aug 25, 2003 at 03:48:32PM -0700, jw schultz wrote:
> On Sun, Aug 24, 2003 at 10:51:20AM +0100, Michael Brown wrote:
> > > > A similar error can occur when open() succeeds but subsequent calls to
> > > > read() fail: under these circumstances rsync will transfer zeroes instead
Hi there
These are the kind of error reports I get from my cron job running rsync:
(the filenames show up as perfectly ok japanese filenames in this mail and
when I browse the linux harddisk via samba)
stat ntprofile/shin/Favorites/ : No such file or directory
mkstemp ntprofile/shin/Favorites
On Tue, Sep 16, 2003 at 11:07:21AM +0900, Dylan Cuthbert wrote:
> Hi there,
>
> I am running rsync in server mode on linux (redhat 8) and I am running
> cygwin (latest version) on a mixture of win2k and winxp machines for
> Japanese users.
>
> When I Rsync from windows rsync complains about a no.
Hi there,
I am running rsync in server mode on linux (redhat 8) and I am running
cygwin (latest version) on a mixture of win2k and winxp machines for
Japanese users.
When I Rsync from windows rsync complains about a no. of Japanese filenames
(not all of them) and this is due,
On Mon, Sep 15, 2003 at 10:18:07AM +0200, Dominik Brettnacher wrote:
> On Sun, 14 Sep 2003, jw schultz wrote:
>
> > The patch won't be effective with the current codebase. I
> > would be inclined to accept a patch that did the fifo. It
> > will take more pursuading for the sockets.
>
> What is
On Sun, 14 Sep 2003, jw schultz wrote:
> The patch won't be effective with the current codebase. I
> would be inclined to accept a patch that did the fifo. It
> will take more pursuading for the sockets.
What is the problem with Andrew's approach?
--
Dominik
"A good piece of technology dream
Jennifer,
I recall getting some error like this when I setup rsync on Solaris 9. I'd
recommed the following:
1. Check the rsync version is the same at both ends.
2. Use option --rsync-path to tell rsync where its friend keeps the binary.
3. Check your runtime library path with crle command at bo
