Dag Wieers wieers.com> writes:
>
> Hi,
>
> I receive this error when rsyncing. I suspect this is because of network
> problems. But the 'Invalid argument' and 'phase unknown' makes it very
> unobvious.
>
> ...
> packages/scribus/scribus-1.2.3-0.rf.src.rpm
> Read from remote
On Thu, Sep 15, 2005 at 04:23:24PM -0700, [EMAIL PROTECTED] wrote:
> https://bugzilla.samba.org/show_bug.cgi?id=3099
>
>
>
>
>
> --- Additional Comments From [EMAIL PROTECTED] 2005-09-15 16:23 ---
> Created an attachment (id=1448)
> --> (https://bugzilla.samba.org/attachment.cgi?id=1
https://bugzilla.samba.org/show_bug.cgi?id=3099
--- Additional Comments From [EMAIL PROTECTED] 2005-09-15 16:23 ---
Created an attachment (id=1448)
--> (https://bugzilla.samba.org/attachment.cgi?id=1448&action=view)
One possible way to reorder the checksum computation.
> how could i
https://bugzilla.samba.org/show_bug.cgi?id=3099
--- Additional Comments From [EMAIL PROTECTED] 2005-09-15 13:49 ---
Pardon me for being dense, but how could it possibly require a change to the
rsync protocol for the second host in the sequence to pre-scan its filesystem,
so that that
Hi,
I encountered a weird file corruption problem with rsync.
I have a perl script that generates and writes a data file to disk, then
rsyncs the file to a remote machine. A perl script running on the remote
machine periodically reads in the data file.
However, occasionally the remote script
Yes, I have received quite a bit of information on the subject.
Thanks.
Gary R. Webster
"Pheneger, Steve" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
09/15/05 01:05 AM
To: rsync@lists.samba.org
cc:
Subject:[rsync] NetEx HyperIP
Hello!
I'm looking t
Hi,
I receive this error when rsyncing. I suspect this is because of network
problems. But the 'Invalid argument' and 'phase unknown' makes it very
unobvious.
...
packages/scribus/scribus-1.2.3-0.rf.src.rpm
Read from remote host rsync.sw.be: Invalid argument
rsyn
On Thu, Sep 15, 2005 at 10:15:51AM -0700, Wayne Davison wrote:
> Attached is a patch that I think effects the change of using link()
> instead of rename() when possible.
That patch had a couple problems with dealing with boundary conditions
(such as cross-device cases and a filesystem that doesn't
On Thu, Sep 15, 2005 at 08:49:33AM -0700, Wayne Davison wrote:
> (At least, that's all the side-effects I can think of off the top of
> my head.)
At least one more was that backing up a directory without a --backup-dir
still requires using rename().
Attached is a patch that I think effects the ch
On Thu, Sep 15, 2005 at 10:38:04AM -0400, Dave Mielke wrote:
> The only change, therefore, should be to replace the first rename()
> with link(). Since both yield EXDEV, I doubt any more complex change
> is necessary.
It's more complex than that. If the temp file is not in a position
where it can
[quoted lines by Dave Mielke on 2005/09/15 at 10:09 -0400]
>[quoted lines by Chris Shoemaker on 2005/09/15 at 09:59 -0400]
>
>>what about when backup-dir is not on same filesystem
>>as original? link will give EXDEV, I think.
>
>Then, as I see it, rsync should go back to using rename but generate
[quoted lines by Chris Shoemaker on 2005/09/15 at 09:59 -0400]
>what about when backup-dir is not on same filesystem
>as original? link will give EXDEV, I think.
Then, as I see it, rsync should go back to using rename but generate a warning.
--
Dave Mielke | 2213 Fox Crescent | I bel
On Thu, Sep 15, 2005 at 08:45:00AM -0400, Dave Mielke wrote:
> When using --backup, the sequence (as monitored by strace) is:
>
>rename("/path/to/", "/")
>rename("/path/to/..xx", "/path/to/")
>
> This, of course, leaves a momentary window wherein can't be found.
> Might
> it be pos
When using --backup, the sequence (as monitored by strace) is:
rename("/path/to/", "/")
rename("/path/to/..xx", "/path/to/")
This, of course, leaves a momentary window wherein can't be found. Might
it be possible to replace the first rename() with link() instead? This, of
course, coul
Hi,
I got the following report from a Debian user:
On Sat 20 Aug 2005, Ross Boylan wrote:
>
> The man page says "a modern rsync uses ssh for its communications"
> (while noting it may have been configure otherwise, but then goes on
> to say (about remote shells) "One common substitute is to use
> Wow, that's unexpected. I had thought that the connection from the
> stunnel process to the rsync process would have been a normal (albeit
> local) socket connection. Perhaps it is not? Or perhaps there is a bug
> that got triggered by this setup. The way rsync works, it has two
> separate pr
On Mon, Sep 12, 2005 at 06:04:16PM -0500, Steve Sether wrote:
> Could this be a problem with Linux? I've tried killing the
> stunnel process (as well as the parent stunnel process) on
> the server, and the rsync process persists.
Wow, that's unexpected. I had thought that the connection from the
On Wed, Sep 14, 2005 at 04:22:01PM -0300, Igor Hjelmstrom Vinhas Ribeiro wrote:
> rsync --config=/home/igor/rsyncd.conf --daemon --server --sender -vr .
> ./somefolder/somewhere
A modern rsync would reject that command-line as invalid (since --sender
and -r aren't daemon options, and paths aren't
On Wed, Sep 14, 2005 at 03:27:13PM -0400, Poe, David wrote:
> /usr/ccs/bin/ld: Unsatisfied symbols:
>_U_Qfneg (first referenced in lib/snprintf.o) (code)
That's a function from HPUX's quadlib.o library (it negates a "long
double" value). It should be a part of your standard C library. I
can'
On Wed, Sep 14, 2005 at 08:51:41PM -0700, Ian Webber wrote:
> rsync: writefd_unbuffered failed to write 4 bytes: phase "unknown" [sender]:
> Connection reset by peer (104)
See the "issues and debugging" page of the website for instructions on
how to go about debugging a failure on the remote end
https://bugzilla.samba.org/show_bug.cgi?id=3099
[EMAIL PROTECTED] changed:
What|Removed |Added
Severity|normal |enhancement
Status|NEW
On Wed, Sep 14, 2005 at 06:53:46PM -0400, Dave Mielke wrote:
> How can I get rsync to write a log record (like --log-format does for
> data transfer) when no content needs to be transferred but attributes
> (owner, group, mode, ...) are changed?
Use -i or put %i into your --log-format. See the 2.
22 matches
Mail list logo
