Hi,
Im mirrorring my mail server, but upon executing the command on the remote
host i can see some permission denied upon opening the users home directory,
and when it happend the remote host doesnt have the proper ownership from
the transferred data.
Please help
Regards,
Michael P. Carel
Syst
Hi to all,
Im just a RSYNC newbie, i've tried to set this up and evaluate. Im trying to
create a mirror of my mail server but what i observed during my test of this
rsync the ownership are being changed(501) when it was downloaded to my
mirror.I have the following test config with my server:
Tomasz Ciolek <[EMAIL PROTECTED]> on 13.11.2001 01:51:25
An: Thomas Schweikle <[EMAIL PROTECTED]>
Kopie:"Tomasz Ciolek Umm loose the spaces between the - and the pattern??
removing spaces changes matching to not match anything at all ---
transferring all files!
Really something wro
Hi again!
Tomasz Ciolek <[EMAIL PROTECTED]> on 13.11.2001 01:21:27
An: Thomas Schweikle <[EMAIL PROTECTED]>
Kopie:
Thema:Re: rsync exclude/include [FIDUCIA virengeprüft - ohne Gewähr,
daß alle bekannten Viren und deren Varianten erkannt wurden.]
> Try dumoping the whole file l
I want to rsync only a small part of a directory tree. I've set up an
exclude and an include file:
exclude holds:
/*
include holds:
/iso/1.5.*/i386
I am calling rsync using
rsync -avz --include-from="include" --exclude-from="exclude"
ftp3.sourceforge.net::/netbsd/iso iso/
but nothing happens.
Don Mahurin [[EMAIL PROTECTED]] writes:
> Perhaps, all that I need is a "--delete-before-update" option that
> just unlinks the file before it starts to write the temp file. Then
> we avoid the possible issues that you raised. I can still see a
> case where --direct-write may be useful (read-wri
On Mon, Nov 12, 2001 at 11:50:01AM -0800, Don Mahurin wrote:
> Perhaps, all that I need is a "--delete-before-update" option that just
> unlinks the file before it starts to write the temp file. Then we avoid the
> possible issues that you raised. I can still see a case where
> --direct-write ma
Apologies for not including this info in the first place!
My rsycn version is:
rsync version 2.4.6 Copyright Andrew Tridgell and Paul Mackerras
And my OS is:
Red Hat Linux release 7.1 (Seawolf)
Kernel 2.4.2-2 on an i686
--jessica
On Fri, Nov 09, 2001 at 08:43:44PM -0800, Jessica Koeppel wrot
Perhaps, all that I need is a "--delete-before-update" option that just unlinks the
file before it
starts to write the temp file. Then we avoid the possible issues that you raised.
I can still see a case where --direct-write may be useful (read-write file in a
read-only dir), but
this is proba
Oh boy, I think you're getting into quite a can of worms there.
At a minimum this option should imply the --partial option because if the
operation is aborted the file will be left partially transferred. Note
that if you're trying to use the rsync rolling checksum algorithm to
minimize bandwidth
I have attached a patch that supports a new "--direct-write" option.
The result of using this option is to write directly to the destination
files, instead of a temporary file first.
The reason this patch is needed is for rsyncing to a device where the
device is full or nearly full.
Say that I
On Fri, Nov 09, 2001 at 10:29:14AM -0700, [EMAIL PROTECTED] wrote:
> I have written an application in perl, to run multiple rsyncs, retrying
> those which fail.
> I have started getting this error on very large modules since i moved to
> the latest CVS version.
>
12 matches
Mail list logo
