On Thu, 2006-02-23 at 00:06 -0500, Peter wrote:
> Now I'm thinking: What if these operations overlap? What can I do to
> prevent this? Or is this even a problem to begin with?
I don't think anything will go seriously wrong, although you may get
some strange effects. The main one is that the bac
https://bugzilla.samba.org/show_bug.cgi?id=3554
Summary: Second copy of same rsync daemon should notice pid file
and quit
Product: rsync
Version: 2.6.7
Platform: All
OS/Version: All
Status: NEW
Severity: n
On Fri, 2006-02-24 at 18:40 -0500, Linus Hicks wrote:
> I did something similar to what lsk is doing a few months back, I believe
> using
> rsync 2.6.5. I wrote a script to query the database for all the datafiles and
> rsync'ed them individually by specifying the full path to the file. What I
On Tue, 2006-02-21 at 11:28 -0500, Carson Gaspar wrote:
> --On Tuesday, February 21, 2006 4:48 PM +0100 Torbjörn Nordling
> <[EMAIL PROTECTED]> wrote:
>
> > Problem:
> > I have two computers (one at work and one home) and I want to keep them
> > identical, but I cannot rsync them directly because
Matt McCutchen wrote:
On Fri, 2006-02-24 at 11:08 -0800, lsk wrote:
/// lsk:- Thanks for the clarification Wayne, in my case no one
would be allowed to use the destination file until the process is
complete. As soon as my destination server is upgraded to the newer
version of rsync whic
On Fri, 2006-02-24 at 14:03 -0800, Wil Morris wrote:
> Workin' on getting rsync setup in a test envioronment and not sure what
> needs to be done on the servers side to be able to perform the backup from
> the HPUX box. I do have the rsync app in place on the HPUX system however
> can't conn
On Fri, 2006-02-24 at 10:45 -0800, Wayne Davison wrote:
> On Thu, Feb 23, 2006 at 11:12:07PM -0500, Matt McCutchen wrote:
> > I have redone get_local_name again (patch attached), this time to
> > enable rsync to remove a file to make way for a destination directory;
>
> I don't wish to do this, as
Workin' on getting rsync setup in a test envioronment and not sure what
needs to be done on the servers side to be able to perform the backup from
the HPUX box. I do have the rsync app in place on the HPUX system however
can't connect to the servers port 22 ... have searched all over the
On Fri, 2006-02-24 at 12:19 -0400, bulia byak wrote:
> Logically, deleting the dst file which does not exist on src amounts
> to "transferring the non-existence" of that file from src to dst.
> Therefore, if files larger or smaller than some size are ignored in
> transfer, they must just as well be
On Fri, 2006-02-24 at 11:08 -0800, lsk wrote:
> /// lsk:- Thanks for the clarification Wayne, in my case no one
> would be allowed to use the destination file until the process is
> complete. As soon as my destination server is upgraded to the newer
> version of rsync which supports --inpla
Thanks! That solution is fine too.
Rsyncd is run as a root daemon while syncing will be performed by a
regular user.
> -Original Message-
> From: Wayne Davison [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 23, 2006 11:18 PM
> To: Jonathan Chen -X (jonachen - The Armada Group, In
Wayne Davison-2 wrote:
>
> On Fri, Feb 24, 2006 at 05:58:26AM -0800, lsk wrote:
>> 2) And Matt could explain little more on what do you mean by "atomicity"
>
> What he meant is that, without --inplace, rsync creates an updated file
> and moves it into place, making the update atomic (i.e. none
On Fri, Feb 24, 2006 at 12:07:05PM +0530, Vijay Ram.C wrote:
>rsync: connection unexpectedly closed (1804855 bytes received so far)
> [receiver]
>rsync: connection unexpectedly closed (39 bytes received so far)
> [generator]
>
> The rsync command line is given as below:
>
On Thu, Feb 23, 2006 at 11:12:07PM -0500, Matt McCutchen wrote:
> I have redone get_local_name again (patch attached), this time to
> enable rsync to remove a file to make way for a destination directory;
I don't wish to do this, as this is not how cp behaves and I want to
keep the behavior the sa
On Fri, Feb 24, 2006 at 05:58:26AM -0800, lsk wrote:
> 2) And Matt could explain little more on what do you mean by "atomicity"
What he meant is that, without --inplace, rsync creates an updated file
and moves it into place, making the update atomic (i.e. none of the
destination files are ever in
On Thu, Jan 19, 2006 at 10:20:48AM -0500, Matt McCutchen wrote:
> I had the understanding that -H used an O(n^2) algorithm to match up
> hard links and it would be prohibitively expensive to use this option on
> a filesystem with about 100,000 files. Is this true?
It used to be true, but is not a
On Fri, Feb 24, 2006 at 10:52:34AM +0100, Daniel Laffien wrote:
> My users are moving files from one dir to another, mainly without
> renaming.
See the detect-renamed.diff patch in the patches dir of a 2.6.7
pre-release for this functionality -- it adds the --detect-renamed
option. This option al
Logically, deleting the dst file which does not exist on src amounts
to "transferring the non-existence" of that file from src to dst.
Therefore, if files larger or smaller than some size are ignored in
transfer, they must just as well be ignored in deleting (much as
--exclude'd files are also excl
https://bugzilla.samba.org/show_bug.cgi?id=1959
--- Comment #14 from [EMAIL PROTECTED] 2006-02-24 08:39 MST ---
I also had the same problem ocurring randomly on large file transfers between
an IDE disk and a disk attached via USB2.0 using RedHat FC4 and rsync version
2.6.4 protocol v
Hello,
On Fri, 2006-02-24 at 05:58 -0800, lsk wrote:
> I am back with the results..here are the options I tried on a 7.0 GB file.
>
> =>No file on target (rm the file on the target and rsync) with "rsync -czv"
> it took 1 hr.
> =>File on target with but header info change on source with "rsync -
I am back with the results..here are the options I tried on a 7.0 GB file.
=>No file on target (rm the file on the target and rsync) with "rsync -czv"
it took 1 hr.
=>File on target with but header info change on source with "rsync -czv" it
took 40 min
=>File on target with but header info chang
(And while I'm in the mood, it would be nice for the man page to
clarify exactly what "fuzzy match" matches, and what it costs. My
guess is that the important case it matches is a file that is
renamed, that it operates through the construction of a hash table
based on file-size/mod-date per dire
On Fri, Feb 24, 2006 at 06:26:09AM +0100, Philippe BEAU wrote:
> I try to add log file = on each module, it was not working.
There is only support for a single log file for the entire daemon or a
single syslog facility. (You'll note that these options are listed
under global options, not module o
23 matches
Mail list logo
