On Tue, May 04, 2004 at 01:41:04PM +1200, Stuart Inglis wrote:
> mkdir -p a/b/c
> then later on tries to create:
> mkdir -p a/b
Thanks for the clarification. I dug into this and I found that some of
the code paths try to call make_bak_dir() without first getting an
ENOENT error. This can cause t
Rsync Issue Solaris8
When performing a simple rsync between servers I was getting the
following error:
root:#> rsync -e ssh -va /export/home/a078479/bob
smmk39:/export/home/a078479/
ksh: rsync: not found
rsync: connection unexpectedly closed (0 bytes read so far)
rsync error: error in rsync pro
Standard newbie issue.
rsh host command (or ssh host command in your case) does so in a fairly
stripped environment, for instance, a small $PATH, which is your issue
(unless rsync isn't even installed on smmk39). rsync has aneasy
workaround for it. add " --rsync-path=/path/on/the/remote/host/t
When I perform a rsync with backup I get 100's of:
make_bak_dir mkdir "/export/giger.back.eary/java/weka/gui" failed:
File exists
make_bak_dir mkdir "/export/giger.backary/java/weka/gui" failed:
File exists
make_bak_dir mkdir "/export/giger.back...ary/java/weka/gui" failed: File
exists
On Tue, May 04, 2004 at 12:19:29PM +1200, Stuart Inglis wrote:
> make_bak_dir mkdir "/export/giger.back.eary/java/weka/gui" failed:
> File exists
Did you check that path? I assume there is a file that is in the way of
a directory that needs to be created. Perhaps this condition just
arose?
Previously I have been using 2.5.7 and have changed 2 days ago to 2.6.2.
Nothing else has changed, so I figured this was just an extra warning
added to 2.6.2.
I am backing up a 750G RAID array. Without knowing the details it's
almost like the --backup-dir option creates a subdirectory
mkdir -
I compiled and installed rsync 2.6.2 from source (the site's download
page) today, under Cygwin 1.5.9-1 / Windows 2000 Professional SP4.
Initial testing shows that it operates properly and smoothly, and that
Wayne's bugfix for the daemon mode / --backup problem I reported earlier
did the trick.
On Mon, May 03, 2004 at 02:30:52PM -0400, Sean M. Kaiser wrote:
> Here's another test.
Works fine for my unmodified 2.6.0. I'm currently left to assume the
modifications that the third-party made to the version of rsync that
you're using are at fault. You should either try an unmodified rsync,
o
The last version to finish and be renamed over the existing target file
would be the one you end up with. No mixing, and no error returned,
either to the winner or the loser, just a perfect copy of the last version
sent, just as if you had two people editing the same file in a single
directory
Wayne Davison <[EMAIL PROTECTED]> writes:
>On Fri, Apr 30, 2004 at 04:19:35PM -0400, Sean M. Kaiser wrote:
>> [skaiser-pbg4:~] localska% /usr/local/bin/rsync --delete --backup
>> --backup-dir=/Users/localskaiser/archive -a /Users/localskaiser/source
>> /Users/localskaiser/target
>
>This command wor
I currently do this with zlibc "Transparently access compressed files."
0.9e. The files are compressed on the disk, but appear uncompress to
all apps including rsync.
Joe
On Sun, 2004-05-02 at 19:55, Martin Pool wrote:
> - Forwarded message from Paulo da Silva <[EMAIL PROTECTED]> -
>
>
Chris here,
I'm protecting myself from receiving spam mail. Clicking the link below will send your
email to me (no need to resend it), and ensure future emails get through. Sorry for
the hassle - I get 100+ junk emails a day so I have to use this.
Just this once, click the link below so I can
G'day,
From: "Mike McCallister" <[EMAIL PROTECTED]>
[...]
> http://rsync.samba.org/ftp/unpacked/rsync/patches/gzip-rsyncable.diff
>
> Since the patch was created a while ago and is not part of the default
> gzip yet, I was wondering if rsync users on this list had any opinions
> on the patch regar
13 matches
Mail list logo
