On Sun, 2008-07-06 at 17:54 -0700, mike wrote:
> On 7/6/08, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> Actually, what happened was it created the local directory, without
> the +x bit set. But I was running it as the owner, which should mean I
> can still read/write/etc. to it.
No, that's not how
On 7/6/08, Matt McCutchen <[EMAIL PROTECTED]> wrote:
> It's almost always a mistake for a directory to grant a user class
> (owner, group, or world) read permission without the corresponding
> execute permission. I recommend that you chmod the nonexecutable source
> directories and fix whatever p
On Sun, 2008-07-06 at 11:27 -0700, mike wrote:
> I am getting a handful of these errors, and I am not sure why. The
> directories in question have rights like this:
>
> drw-r--r-- 2 osstbb osstbb 42 2008-05-02 00:04 12981826/
> rsync: recv_generator: failed to stat
> "/home/backups/linux01/home/
> > I'd like to see the create times and fileflags patches included so all
> > metadata tests pass with backup bouncer 'out of the box' on Mac OS X.
>
> Those patches are Mac-specific, so I'm pretty sure they won't go into
> the main rsync, but it would make sense to include them in packagings of
I am getting a handful of these errors, and I am not sure why. The
directories in question have rights like this:
drw-r--r-- 2 osstbb osstbb 42 2008-05-02 00:04 12981826/
As root, why would it matter if it has executability? I can read it
just fine on the server.
Or is it an issue when it tries
On 7/4/2008, Wayne Davison ([EMAIL PROTECTED]) wrote:
Other things in the patches dir, suggestions made here, and enhancement
requests from bugzilla will all be reviewed for possible inclusion.
I'd still like to see the --ignore-case patch to be made part of the
official rsync source...
--
