On Sat, 29 Mar 2008 23:08:32 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 29, 2008 at 04:18:57PM -0400, Erik Jan Tromp wrote:
> > I've done some experimenting locally & narrowed things down. In
> > essense, I'm tripping over subtle chan
On Fri, 28 Mar 2008 19:04:27 -0400
Erik Jan Tromp <[EMAIL PROTECTED]> wrote:
> Just tripped over this one today.
>
> $ rsync --no-motd rsync://alphageek.dyndns.org/slackware
> rsync: link_stat "." (in slackware) failed: No such file or directory (2)
> rsync
Just tripped over this one today.
$ rsync --no-motd rsync://alphageek.dyndns.org/slackware
rsync: link_stat "." (in slackware) failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(1498)
[receiver=3.0.1pre2]
$ rsync --no-motd rsync://alphageek
On Fri, 26 Oct 2007 22:15:03 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> Yes, this is something I noticed just a little bit ago myself. I've
> fixed the bug and am in the process of releasing pre4 now. Sorry for
> the inconvenience.
pre4 is working fine for me. No worries about the inconve
I upgraded to pre3 a couple hours ago & right now I'm watching my 00:00
backup set absolutely _crawl_. Typically, backups would have been
finished somewhere in the 00:10 to 00:30 range, depending how much data
changed across 6 machines in the past day. As I write this, the 3rd of 6
machines is (hop
On Thu, 18 Oct 2007 07:06:40 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> I haven't been able to reproduce the error, but I believe I found its
> cause. Please try the latest CVS version and see if it works.
> Thanks!
Pardon the long delay - had my test rig torn down for other projects.
I
On Mon, 15 Oct 2007 23:15:34 -0400
"Matt McCutchen" <[EMAIL PROTECTED]> wrote:
> On 10/15/07, Erik Jan Tromp <[EMAIL PROTECTED]> wrote:
> > # The second error
> > Invalid file index: -101 (-1 - 0) with iflags 0 [receiver]
> > rsync error: proto
Just a quick heads up to say I'm still getting this (reproducable) error while
doing daily backups:
rsync: generator.c:1872: check_for_finished_files: Assertion `flist != ((void
*)0)' failed.
rsync: writefd_unbuffered failed to write 4092 bytes [receiver]: Broken pipe
(32)
rsync error: error in
# The first error
rsync: generator.c:1867: check_for_finished_files: Assertion `flist != ((void
*)0)' failed.
rsync: writefd_unbuffered failed to write 4092 bytes [receiver]: Broken pipe
(32)
rsync error: error in rsync protocol data stream (code 12) at io.c(1493)
[receiver=3.0.0pre2]
# Sample
3.0.0pre2: non-recursive remote listing breakage
Looks like pre1's fix broke something else.
I noticed this when listing module/directory contents on servers known
to be running versions 2.5.7 & 2.6.3. Not having (full) access to them,
I replicated the errors using 2 machines on my home lan.
#
It would appear something snuck in that breaks non-recursive remote
listings when talking to a non-3.0.0pre1 version of rsync. The symptom
itself is simple enough to see; rather than displaying member
directories/regular files/symlinks/etc as one would expect, only
non-directories (with the excepti
Wayne,
I've been experimenting with the {pre,post}-xfer exec options ever since the
original diff showed up in patches/ - fantastic stuff.
My feature request/change centers around the new RSYNC_ARG# variables. Would it
be possible to make these available as an array (ie: ${RSYNC_ARG[#]}) rather
On Thu, 28 Jul 2005 19:40:55 -0400
Erik Jan Tromp <[EMAIL PROTECTED]> wrote:
> On Thu, 28 Jul 2005 13:09:01 -0700
> Wayne Davison <[EMAIL PROTECTED]> wrote:
>
> > I have released rsync version 2.6.6.
>
> I just extracted the 2.6.6 source tarball & notic
On Thu, 28 Jul 2005 13:09:01 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> I have released rsync version 2.6.6.
I just extracted the 2.6.6 source tarball & noticed that
patches/pre-post-exec.diff wasn't applied to trunk. Wups?
--
"I really want a license to do just two things: make the code
On Tue, 19 Jul 2005 18:06:59 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Tue, Jul 19, 2005 at 06:27:56PM -0500, Evan Harris wrote:
> > Is it possible that this patch might be added to the mainstream
> > release anytime soon?
>
> I was originally against the idea, but have softened my oppo
On Sat, 11 Jun 2005 23:22:39 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> OK, the crash turned out to be caused by an empty file-list not getting
> its "high" value set correctly. If such an empty list gets passed to
> flist_find(), it would crash. This is not something that normally
> happe
On Sat, 11 Jun 2005 09:03:07 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
> On Fri, Jun 10, 2005 at 05:14:57AM -0400, Erik Jan Tromp wrote:
> > if I remove every possible option except --fuzzy & --link-dest,
> > segfault every time.
>
> I haven't seen that
Continuing with my backup script (see previous post), I've found a small oops
regarding the 'max verbosity' option for rsyncd.conf
In the manpage this option is listed as a module option. Poking through the
source, however, shows that it's parsed as a global option (loadparm.c).
If it's a quest
I've been reworking my backup script & decided to give some of the newer
options a try. It would appear I've found a combination that doesn't play nice.
$ rsync --archive --delete-during --fuzzy --hard-links --numeric-ids
--quiet --sparse --temp-dir /backup/helium/
--link-dest /backup/hydrogen/
On Fri, 27 May 2005 16:22:52 +0200
David Hausheer <[EMAIL PROTECTED]> wrote:
> Is there a way to backup files to a remote machine on which I don't have
> root permission, while preserving their uids/gids? I know that only the
> super-user can set the owner and group of a file, so what I am actua
On Wed, 18 May 2005 14:33:33 -0400
greg fenton <[EMAIL PROTECTED]> wrote:
> I am looking to move files from one system to another (rather than
> copy).
heya gregf
Assuming you have rsync 2.6.4 or newer available to you, "--remove-sent-files"
is likely what you're after.
Erik
--
"I really wan
On Fri, 22 Apr 2005 09:08:38 -0700
Wayne Davison <[EMAIL PROTECTED]> wrote:
First up, sorry about the dup'd post.. just me being braindead at that hour.
> It would help to know what rsync was doing with the files when the error
> happened, if all the hard-links for a particular hard-link group ar
The background:
I host one of the unofficial slackware mirrors & push to a high speed
(unlisted) mirror that several other unofficials use for pulls. To save
time/disk/bandwidth I use a custom script to hardlink the trees prior to
pushing the updates to said unlisted mirror.
The commandline (l
The background:
I host one of the unofficial slackware mirrors & push to a high speed
(unlisted) mirror that several other unofficials use for pulls. To save
time/disk/bandwidth I use a custom script to hardlink the trees prior to
pushing the updates to said unlisted mirror.
The commandline (l
On Mon, 28 Mar 2005 23:16:59 -0800
Wayne Davison <[EMAIL PROTECTED]> wrote:
> I've released rsync 2.6.4pre4. I believe that this version will be what
> gets released as 2.6.4, hopefully on Wednesday. Please try this out
> and let me know if anything is amiss.
I just noticed an oddity when usi
On Wed, 16 Mar 2005 16:53:01 -0800
Wayne Davison <[EMAIL PROTECTED]> wrote:
> This is a result of a 1-character typo in options.c:
> I've checked this in. Thanks for the report!
Wow, talk about fast turnaround. :)
Patched, rebuilt, & tested here. Works like a charm. Keep up the fantastic work.
Synopsis: Prior to the 2.6.4pre versions, issuing 'rsync rsync://host/module/'
behaved effectively as 'ls -l'. I've toyed with various options in an attempt
to get an 'ls -l' style output, but to no avail.
As I have a small handful of scripts that rely on this no-longer-functioning
functionalit
On Wed, 26 Jan 2005 18:12:54 +0100
<[EMAIL PROTECTED]> wrote:
> I can't find the difference, every file has on both systems the same size,
> I'didn't found
> any hidden files (rsync archive?) or something like that. Has anywone an idee,
> why there is a difference of 10 kilobytes?
Check the si
On Wed, 22 Sep 2004 13:21:31 +0200
Paul Slootman <[EMAIL PROTECTED]> wrote:
> > I had hoped to use it both for my rotating backups & for my (unofficial)
> > slackware mirror.
>
> Hmmm... For a slackware mirror I expect that it would be fine.
To my eyes, a mirror implies a duplicate fileset indis
I had noticed the --link-by-hash patch a short while back & decided it was time to
experiment with it. Sadly, its behaviour is considerabely different from what I
expected - to the point that I find it unusable in its current form. I had hoped to
use it both for my rotating backups & for my (uno
Oops :)
-- quote --
$ rsync -aHPv rsync://host/module/single.file .
receiving file list ...
1 file to consider
Segmentation fault
-- endquote --
The rsync process remains running until explicitly 'kill'ed. At which point, the
following is printed:
-- quote --
rsync error: received SIGUSR1 or
31 matches
Mail list logo
