Re: delete fails to delete everything it should like dangling symlinks

[Phil Howard]

On Fri, Mar 08, 2002 at 09:46:46AM -0700, [EMAIL PROTECTED] wrote:

| Try it without "--delete-after".  I'm pretty sure that --delete-after also 
| affects --force, so I think it's trying to write to the directory pointed 
| to by the symlink, which doesn't exist.  I could be wrong, but that looks 
| like the most likely interaction.

Same problem:

=
root@pollux:/home/root/src 347> rsync --checksum --copy-unsafe-links --compress 
'--exclude=*~' '--exclude=#*#' --force --group --links --owner --partial --perms 
--progress --recursive --timeout=150 --times --verbose --delete --delete-excluded 
--ignore-errors --force /home/root/src-pub/ /home/root/src/
rsync: building file list...
rsync: 809 files to consider.
readlink openssl-0.9.6b/work/openssl-0.9.6b/crypto/des/asm/perlasm: No such file or 
directory
readlink openssl-0.9.6c/tmp/openssl-0.9.6c/crypto/des/asm/perlasm: No such file or 
directory
wrote 34720 bytes  read 20 bytes  2395.86 bytes/sec
total size is 85523958  speedup is 2461.83
rsync error: partial transfer (code 23) at main.c(576)
root@pollux:/home/root/src 348>
=

The --copy-unsafe-links seems to be the culprit.  If I take that out it then
works to delete these symlinks.  ATM I can't recall why I put that in.  I'm
sure I'll find out soon enough unless it was some bug from an older version
that is now fixed.

-- 
-
| Phil Howard - KA9WGN |   Dallas   | http://linuxhomepage.com/ |
| [EMAIL PROTECTED] | Texas, USA | http://phil.ipal.org/ |
-

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: rsync with -ls option

[George . R . Goffe]

Dave,

Unfortunately I don't do much coding so I don't think I'm the "right" guy
for this job. I'd like to see the emails tho, MAYBE I can cook something
up. I was actually thinking about making the "report" even more sexy by
what I call the "rdiff" function. Rsync compares files now and might be
able to make pipes to diff? Of course binaries would not be eligible.

What do you think?

Regards,

George...





Dave Dykstra <[EMAIL PROTECTED]> on 03/08/2002 09:57:51 AM

To:   [EMAIL PROTECTED]
cc:   [EMAIL PROTECTED]

Subject:  Re: rsync with -ls option


A long time ago somebody volunteered to improve the --log-format and -n
options to work for those kind of situations but he never did them.  So
we're waiting for a new volunteer.  If somebody else is interested in doing
them I could dig up the old emails where we discussed some of the design.

- Dave Dykstra

On Sat, Mar 02, 2002 at 06:30:45AM -0800, [EMAIL PROTECTED] wrote:
> Howdy,
>
> I'm trying to get a report from rsync using the -n option which will
> produce a report of files that are different in a ls -al kind of style so
> one could analyze what's different before possibly clobering a good file.
>
> Is this possibly in the works or does anyone have any ideas on how this
> might be done. It seems like a useful option to rsync to have.
>
> Regards,
>
> George...
>
>
>
>
> --
> To unsubscribe or change options:
http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read:
http://www.tuxedo.org/~esr/faqs/smart-questions.html





-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: [PATCH][RFC] space saving incrementals

[jw schultz]

On Fri, Mar 08, 2002 at 03:45:04PM -0600, Dave Dykstra wrote:
> I like link-dest, and the "-" for exclude-from/include-from was already
> something I was planning to add one of these days along with the
> --files-from option I still plan to write, but --compare-perms confuses
> me.  Can you give examples of when you need it?
> 
> - Dave Dykstra

sequence of commands:
admin# rsync /project /vault/monday
admin# chmod 666 /project/somefile
admin# chown bin /project/someotherfile
admin# rsync --link-dest=/vault/monday /project /vault/tuesday

Now /vault/monday/somefile has perms of 666 and
someotherfile is owned by bin.  I cannot restore the perms
from /vault/monday.  That info is lost. /vault/monday no
longer is an accurate representative of what existed when it
was created.

With --compare-perms somefile and someotherfile will not be
linked between monday and tuesday even though the contents
haven't changed.

compare-perms only makes sense when you are using link-dest.


> 
> On Thu, Mar 07, 2002 at 01:25:50PM -0800, jw schultz wrote:
> > Please CC me directly as i'm not on the list.
> > 
> > I have attached a patch against latest CVS (cvs diff -u)
> > that adds the following functionality.  I can break it up if
> > you would prefer it in pieces.  Comments welcome.
> > 
> > o add compare-perms option
> > This creates a new inode for a file even if only
> > the perms have changed.  This way if a file
> > outside of destdir is hardlinked to a dentry
> > inside destdir the permissions (uid, gid,
> > mode) will be untouched preserving history
> > etc.
> > 
> > o link-dest option
> > After setting compare_dest this causes
> > unchanged files in destdir to be hardlinked
> > to link-dest.
> > 
> > o modified make_exclude_list to support stdin
> > if --exclude-from has argument of "-"
> > stdin will be read.
> > This lets us pipe a include/exclude list
> > into rsync so that we can generate it on the
> > fly.
> > 
> > The upshot of these is to allow rsync to make incremental
> > backups without modifying earlier versions but keep every
> > version as a complete tree.  It then becomes possible to
> > make tapes or restore from any image.
> > 
> > Although --compare-perms saves on block count this patch
> > only applies it to regular files so symlinks and device
> > nodes will still chew up inodes. :( 
> > 
> > for the sake of an example here is the command line i'm using:
> > /site/bin/rsync -v --stats -a -H -e ssh --compare-perms
> > --delete --delete-excluded --numeric-ids --exclude-from -
> > --link-dest /e/backup1/home/update1/tree leto:/efs/home/
> > /e/backup1/home/update2/tree > /e/backup1/home/update2/log
> > 
> > i have tried to keep my changes small and consistent with the
> > existing coding style.  Feel free to dink with it.  I only
> > care about the performance.
> > 
> > 

-- 

J.W. SchultzPegasystems Technologies
email address:  [EMAIL PROTECTED]

Remember Cernan and Schmitt

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: [PATCH][RFC] space saving incrementals

[Dave Dykstra]

I like link-dest, and the "-" for exclude-from/include-from was already
something I was planning to add one of these days along with the
--files-from option I still plan to write, but --compare-perms confuses
me.  Can you give examples of when you need it?

- Dave Dykstra

On Thu, Mar 07, 2002 at 01:25:50PM -0800, jw schultz wrote:
> Please CC me directly as i'm not on the list.
> 
> I have attached a patch against latest CVS (cvs diff -u)
> that adds the following functionality.  I can break it up if
> you would prefer it in pieces.  Comments welcome.
> 
>   o add compare-perms option
>   This creates a new inode for a file even if only
>   the perms have changed.  This way if a file
>   outside of destdir is hardlinked to a dentry
>   inside destdir the permissions (uid, gid,
>   mode) will be untouched preserving history
>   etc.
> 
>   o link-dest option
>   After setting compare_dest this causes
>   unchanged files in destdir to be hardlinked
>   to link-dest.
> 
>   o modified make_exclude_list to support stdin
>   if --exclude-from has argument of "-"
>   stdin will be read.
>   This lets us pipe a include/exclude list
>   into rsync so that we can generate it on the
>   fly.
> 
> The upshot of these is to allow rsync to make incremental
> backups without modifying earlier versions but keep every
> version as a complete tree.  It then becomes possible to
> make tapes or restore from any image.
> 
> Although --compare-perms saves on block count this patch
> only applies it to regular files so symlinks and device
> nodes will still chew up inodes. :( 
> 
> for the sake of an example here is the command line i'm using:
>   /site/bin/rsync -v --stats -a -H -e ssh --compare-perms
>   --delete --delete-excluded --numeric-ids --exclude-from -
>   --link-dest /e/backup1/home/update1/tree leto:/efs/home/
>   /e/backup1/home/update2/tree > /e/backup1/home/update2/log
> 
> i have tried to keep my changes small and consistent with the
> existing coding style.  Feel free to dink with it.  I only
> care about the performance.
> 
> 
> -- 
> 
>   J.W. SchultzPegasystems Technologies
>   email address:  [EMAIL PROTECTED]
> 
>   Remember Cernan and Schmitt

> Index: exclude.c
> ===
> RCS file: /cvsroot/rsync/exclude.c,v
> retrieving revision 1.42
> diff -u -r1.42 exclude.c
> --- exclude.c 18 Feb 2002 19:10:28 -  1.42
> +++ exclude.c 7 Mar 2002 20:56:02 -
> @@ -219,8 +219,14 @@
> int fatal, int include)
>  {
>   struct exclude_struct **list=list1;
> - FILE *f = fopen(fname,"r");
> + FILE *f;
>   char line[MAXPATHLEN];
> +
> + if (strcmp(fname, "-")) {
> + f = fopen(fname,"r");
> + } else {
> + f = fdopen(0, "r");
> + }
>   if (!f) {
>   if (fatal) {
>   rsyserr(FERROR, errno,
> Index: generator.c
> ===
> RCS file: /cvsroot/rsync/generator.c,v
> retrieving revision 1.33
> diff -u -r1.33 generator.c
> --- generator.c   7 Feb 2002 16:36:12 -   1.33
> +++ generator.c   7 Mar 2002 20:56:02 -
> @@ -42,6 +42,8 @@
>  extern int always_checksum;
>  extern int modify_window;
>  extern char *compare_dest;
> +extern int compare_perms;
> +extern int link_dest;
>  
>  
>  /* choose whether to skip a particular file */
> @@ -51,6 +53,15 @@
>   if (st->st_size != file->length) {
>   return 0;
>   }
> + if (compare_perms) {
> + if((st->st_mode & ~_S_IFMT) !=  (file->mode & ~_S_IFMT)) {
> + return 0;
> + }
> + if (st->st_uid != file->uid || st->st_gid != file->gid) {
> + return 0;
> + }
> + }
> +
>   
>   /* if always checksum is set then we use the checksum instead 
>  of the file time to determine whether to sync */
> @@ -352,6 +363,17 @@
>   statret = -1;
>   if (statret == -1)
>   errno = saveerrno;
> +#if HAVE_LINK
> + else if (link_dest)
> + if (do_link(fnamecmpbuf, fname) != 0) {
> + if (verbose > 0)
> + rprintf(FINFO,"link %s => %s : %s\n",
> + fnamecmpbuf,
> + fname,
> + strerror(errno));
> + fnamecmp = fnamecmpbuf;
> + }
> +#endif
>   else
>   fnamecmp = fnamecmpbuf;
>   }
> Index: options.c
> ===

Re: how to prevent forward/reverse lookups

[Dave Dykstra]

The 2.5.3 "preview" versions do that differently than previous versions;
please try that and see if you still want to prevent those lookups and
if so explain why.

- Dave Dykstra

On Tue, Mar 05, 2002 at 08:03:53PM -0800, plug bert wrote:
> Hello All,
> 
> A good day to you all. Is there any way to prevent
> the rsyncd daemon f rom performing the forward/reverse
> lookups for rsync clients?
> 
> 
> Thanks in advance.
> 
> 
> 
> 
> 
> __
> Do You Yahoo!?
> Try FREE Yahoo! Mail - the world's greatest free email!
> http://mail.yahoo.com/
> 
> -- 
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: Error messages

[Dave Dykstra]

Don't use rsync 2.5.2, it's got some serious problems.  They're fixed in
the 2.5.3pre* versions in the "preview" directory on the rsync sources
download site.  Unfortunately we don't make binaries except for released
versions releases though, sorry.

The Solaris251 binaries in the rsync binaries area should work on all
SunOS 5.5.1 and later, yes.

- Dave Dykstra


On Tue, Mar 05, 2002 at 01:55:58PM -0800, Jennifer Lu wrote:
> 
> 
> 
> Hi,
> 
> We got the following error messages when we ran rsync 2.5.2
> from Solaris-5.5.1 to Solaris-5.8.
> 
> vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/systop.v
> vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/sysup_esat.v
> vl121909/jagcdms_ch+_diags/sys/sys_l/ch_sys/rtl/upesat_defines.h
> wrote 63878001383 bytes  read 1529124 bytes  1246928.64 bytes/sec
> total size is 148182624008  speedup is 2.32
> rsync error: partial transfer (code 23) at main.c(576)
> 
> I have downloaded rsync-2.3.2.tar.gz & rsync-2.5.2.Solaris251.sparc.tar.gz, 
> is rsync-2.5.2.Solaris251.sparc.tar.gz mainly for Solaris5.5.1.1? 
> This file already has rsync binary, so I don't need to re-compile it, right?
> 
> Thanks for the help,
> Jennifer
> 
> 
> -- 
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: Compile 2.5.2 on RedHat 6.2

[Dave Dykstra]

That's a known problem, solved in the 2.5.3pre* versions in the "preview"
area of the rsync download site.

- Dave Dykstra

On Thu, Mar 07, 2002 at 05:03:02PM -0800, Matt Simonsen wrote:
> OK - that's 3 individuals with Redhat 6.2 installs who have encountered this.
> I'm pretty sure it's a real problem (ie I can duplicate it and others have
> had it, too).
> 
> Is there a more appropriate place to submit this bug or something that I can
> do to help have it fixed? I am not competent to debug the C code, but I am
> willing and able to provide any debugging info.
> 
> Thanks!
> Matt
> 
> On Thursday 07 March 2002 03:19 pm, Scott Russell wrote:
> > For what it's worth I saw the same error. 2.5.1 worked fine however.
> > I never found a solution.
> >
> > -- Scott
> >
> > In mailinglists.external.rsync, you wrote:
> > > I am running RedHat 6.2 on many of my servers and am receiving the
> > > following errors when compiling Rsync 2.5.2:
> > >
> > > [root@wrapguy rsync-2.5.2]# make
> > > gcc -I. -I. -g -O2 -DHAVE_CONFIG_H -Wall -W -c rsync.c -o rsync.o
> > > In file included from rsync.c:23:
> > > rsync.h:339: warning: no semicolon at end of struct or union
> > > rsync.h:339: parse error before `inode'
> > > rsync.h:341: parse error before `dev'
> > > rsync.h:341: warning: type defaults to `int' in declaration of `dev'
> > > rsync.h:341: warning: data definition has no type or storage class
> > > rsync.h:344: parse error before `rdev'
> > > rsync.h:344: warning: type defaults to `int' in declaration of `rdev'
> > > rsync.h:344: warning: data definition has no type or storage class
> > > rsync.h:347: `basename' redeclared as different kind of symbol
> > > /usr/include/string.h:317: previous declaration of `basename'
> > > rsync.h:350: `link' redeclared as different kind of symbol
> > > /usr/include/unistd.h:678: previous declaration of `link'
> > > rsync.h:352: parse error before `}'
> > > rsync.h: In function `flist_up':
> > > rsync.h:420: dereferencing pointer to incomplete type
> > > rsync.c: In function `set_perms':
> > > rsync.c:165: dereferencing pointer to incomplete type
> > > rsync.c:168: dereferencing pointer to incomplete type
> > > rsync.c:178: dereferencing pointer to incomplete type
> > > rsync.c:179: dereferencing pointer to incomplete type
> > > rsync.c:179: dereferencing pointer to incomplete type
> > > rsync.c:184: dereferencing pointer to incomplete type
> > > rsync.c:188: dereferencing pointer to incomplete type
> > > rsync.c:189: dereferencing pointer to incomplete type
> > > rsync.c:206: dereferencing pointer to incomplete type
> > > rsync.c:208: dereferencing pointer to incomplete type
> > > rsync.c:152: warning: `change_uid' might be used uninitialized in this
> > > function
> > > rsync.c:152: warning: `change_gid' might be used uninitialized in this
> > > function
> > > rsync.c: In function `finish_transfer':
> > > rsync.c:245: dereferencing pointer to incomplete type
> > > make: *** [rsync.o] Error 1
> 
> ---
> 
> --
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: An NT problem?

[Dave Dykstra]

On Mon, Mar 04, 2002 at 08:30:04PM -0500, Mike Westkamper wrote:
> 
> Gentlemen;
> 
> I installed the Cygwin/Rsync on NT per
> http://optics.ph.unimelb.edu.au/help/rsync/
> 
> When trying to access it from a linux machine I always get:
> 
> [root@auxfs backups]# rsync rsync://192.168.1.205/ .
> read error: Connection reset by peer
> [root@auxfs backups]#

rsync:// requires the rsync daemon to be running on 192.168.1.205 on port 873.

> OR
> 
> [root@auxfs backups]# rsync 192.168.1.205:/ .
> 192.168.1.205: Connection refused
> unexpected EOF in read_timeout
> [root@auxfs backups]#

That method requires rsh to 192.168.1.205 to work.


> Any suggestions will be greatly appreciated.
> 
> Mike

- Dave Dykstra

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: 4.4BSD chflags support for rsync

[Rolf Grossmann]

Hi Dave,

on Fri, 8 Mar 2002 11:55:10 -0600 Dave Dykstra wrote 
concerning "Re: 4.4BSD chflags support for rsync" something like this:

> New options are usually handled by just letting the remote side fail when
> it doesn't understand the option, as you're doing.  Perhaps you just
> shouldn't include it with -a.

Ok, changed that. I also put a note in the manpage.

> At a minimum, you'd need to update the rsync.yo and rsync.1 versions of
> the man page before it could be accepted.

Heh, I knew I forgot something. ;) I've updated the patch. When building
the new rsync.1 manpage, an entry about --ignore-existing was also included
and is contained in my patch.

Please let me know what you think.

Thanks, Rolf

> On Fri, Mar 01, 2002 at 07:12:47PM +0100, [EMAIL PROTECTED] wrote:
>> Hi,
>> 
>> I've changed rsync to support the BSD change file flags. However, this
>> raises some compatibility problems, especially when including it with
>> the -a option. If the remote host does not understand the new option
>> for updating file flags, the user gets an error message about an
>> unknown option. How should I handle this?
>> 
>> If you'd like to look at the patch (and preferably integrate it with the
>> main source ;)) you can get it at http://www.progtech.net/rsync.flags-patch
>> All comments are welcome, but please CC me directly as I'm not on the list.
>> 
>> Thanks and bye,
>> Rolf

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: Solaris, socketpair and chroot

[Dave Dykstra]

On Sun, Mar 03, 2002 at 07:26:14PM +0100, Thomas Quinot wrote:
> Le 2002-02-27, Dave Dykstra ?crivait :
> 
> > That wouldn't be very friendly to have to do for every module listed in
> > rsyncd.conf.
> 
> Yep, hence my report :)
> 
> > It would be interesting to do for a test though just to make
> > sure that this is really the problem.  I'm surprised that no-one else would
> > have reported this before.  Surely it can't be needed on all versions of
> > Solaris.
> 
> I can confirm that, on a system that exhibits the problem, just
> doing a mknod for /dev/ticotsord in the chroot'd volume resolves it.
> 
> Thomas.


Well, then, if somebody would submit a patch it could be considered.

- Dave Dykstra

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: rsync with -ls option

[Dave Dykstra]

A long time ago somebody volunteered to improve the --log-format and -n
options to work for those kind of situations but he never did them.  So
we're waiting for a new volunteer.  If somebody else is interested in doing
them I could dig up the old emails where we discussed some of the design.

- Dave Dykstra

On Sat, Mar 02, 2002 at 06:30:45AM -0800, [EMAIL PROTECTED] wrote:
> Howdy,
> 
> I'm trying to get a report from rsync using the -n option which will
> produce a report of files that are different in a ls -al kind of style so
> one could analyze what's different before possibly clobering a good file.
> 
> Is this possibly in the works or does anyone have any ideas on how this
> might be done. It seems like a useful option to rsync to have.
> 
> Regards,
> 
> George...
> 
> 
> 
> 
> -- 
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: 4.4BSD chflags support for rsync

[Dave Dykstra]

New options are usually handled by just letting the remote side fail when
it doesn't understand the option, as you're doing.  Perhaps you just
shouldn't include it with -a.

At a minimum, you'd need to update the rsync.yo and rsync.1 versions of
the man page before it could be accepted.

- Dave Dykstra

On Fri, Mar 01, 2002 at 07:12:47PM +0100, [EMAIL PROTECTED] wrote:
> Hi,
> 
> I've changed rsync to support the BSD change file flags. However, this
> raises some compatibility problems, especially when including it with
> the -a option. If the remote host does not understand the new option
> for updating file flags, the user gets an error message about an
> unknown option. How should I handle this?
> 
> If you'd like to look at the patch (and preferably integrate it with the
> main source ;)) you can get it at http://www.progtech.net/rsync.flags-patch
> All comments are welcome, but please CC me directly as I'm not on the list.
> 
> Thanks and bye,
> Rolf
> 
> -- 
> To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
> Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

-- 
To unsubscribe or change options: http://lists.samba.org/mailman/listinfo/rsync
Before posting, read: http://www.tuxedo.org/~esr/faqs/smart-questions.html

Re: delete fails to delete everything it should like dangling symlinks

[tim . conway]

Try it without "--delete-after".  I'm pretty sure that --delete-after also 
affects --force, so I think it's trying to write to the directory pointed 
to by the symlink, which doesn't exist.  I could be wrong, but that looks 
like the most likely interaction.

Tim Conway
[EMAIL PROTECTED]
303.682.4917
Philips Semiconductor - Longmont TC
1880 Industrial Circle, Suite D
Longmont, CO 80501
Available via SameTime Connect within Philips, n9hmg on AIM
perl -e 'print pack(, 
19061,29556,8289,28271,29800,25970,8304,25970,27680,26721,25451,25970), 
".\n" '
"There are some who call me Tim?"




Phil Howard <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
03/07/2002 11:35 PM

 
To: [EMAIL PROTECTED]
cc: (bcc: Tim Conway/LMT/SC/PHILIPS)
Subject:delete fails to delete everything it should like dangling 
symlinks
Classification: 



I think someone posted this before, but I can't find it in the archives.

I am using rsync to pull down source files to be compiled.  The delete
options are used to clear out any old files left over from previous.
Normally this works.  I've run into one case where it persistently fails.

Within the directory created during compiling is a symlink to another
directory, also created during compiling (well, literally, during tar
extraction done by the script that does the compiling).  When rsync is
run to re-syncronize, which should delete all created files (including
all those extracted from the tar file), the directory that is the target
of the symlink apparently is deleted first.  Then when the symlink is
encountered, I get an error saying that readlink gets No such file or
directory.  This doesn't make sense since readlink should work on a
dangling link.

Here's a paste of manually doing the rsync within the same host
(warning, the first line is 318 characters long):

=
root@pollux:/home/root/src 152> rsync --checksum --copy-unsafe-links 
--compress '--exclude=*~' '--exclude=#*#' --force --group --links --owner 
--partial --perms --progress --recursive --timeout=150 --times --verbose 
--delete --delete-after --delete-excluded --ignore-errors --force 
/home/root/src-pub/ /home/root/src/
rsync: building file list...
rsync: 809 files to consider.
readlink openssl-0.9.6b/work/openssl-0.9.6b/crypto/des/asm/perlasm: No 
such file or directory
readlink openssl-0.9.6c/tmp/openssl-0.9.6c/crypto/des/asm/perlasm: No such 
file or directory
wrote 34720 bytes  read 20 bytes  4087.06 bytes/sec
total size is 85523954  speedup is 2461.83
rsync error: partial transfer (code 23) at main.c(576)
root@pollux:/home/root/src 153> readlink 
openssl-0.9.6c/tmp/openssl-0.9.6c/crypto/des/asm/perlasm
../../perlasm
root@pollux:/home/root/src 154> rsync --version
rsync  version 2.5.2  protocol version 26
Copyright (C) 1996-2002 by Andrew Tridgell and others

Capabilities: 64-bit files, socketpairs, hard links, symlinks, batchfiles, 
IPv6,
  32-bit system inums, 64-bit internal inums
root@pollux:/home/root/src 155>
=

As you can see I'm using a number of options that should, according
to the man page, make sure things get deleted.  But this is not
happening.

I assume that "partial transfer (code 23)" error message is because
it did recognize that it failed to completely get things in sync.

BTW, after manually deleting the 2 symlinks, it works fine:

=
root@pollux:/home/root/src 155> rm -f 
openssl-0.9.6b/work/openssl-0.9.6b/crypto/des/asm/perlasm
root@pollux:/home/root/src 156> rm -f 
openssl-0.9.6c/tmp/openssl-0.9.6c/crypto/des/asm/perlasm
root@pollux:/home/root/src 157> rsync --checksum --copy-unsafe-links 
--compress '--exclude=*~' '--exclude=#*#' --force --group --links --owner 
--partial --perms --progress --recursive --timeout=150 --times --verbose 
--delete --delete-after
--delete-excluded --ignore-errors --force /home/root/src-pub/ 
/home/root/src/
rsync: building file list...
rsync: 809 files to consider.
deleting directory openssl-0.9.6c/tmp/openssl-0.9.6c/crypto/des/asm
deleting directory openssl-0.9.6c/tmp/openssl-0.9.6c/crypto/des
deleting directory openssl-0.9.6c/tmp/openssl-0.9.6c/crypto
deleting directory openssl-0.9.6c/tmp/openssl-0.9.6c
deleting directory openssl-0.9.6c/tmp
deleting directory openssl-0.9.6b/work/openssl-0.9.6b/crypto/des/asm
deleting directory openssl-0.9.6b/work/openssl-0.9.6b/crypto/des
deleting directory openssl-0.9.6b/work/openssl-0.9.6b/crypto
deleting directory openssl-0.9.6b/work/openssl-0.9.6b
deleting directory openssl-0.9.6b/work
wrote 34720 bytes  read 20 bytes  4087.06 bytes/sec
total size is 85523954  speedup is 2461.83
root@pollux:/home/root/src 158>
=

-- 
--

Compiling on a Cobalt RaQ1

[Jurrie Overgoor]

Hello,
 
I've downloaded version 2.5.2 and I tried compiling that one 
on a Cobalt RaQ1 server (maybe anyone has heard of them, they have that neat 
blue front). What I want is to make the RaQ1 a remote backup server, so I 
thought Rsync would be usefull...
The compilation did not work, it stalled trying to compile 
clientserver.c (or something, I cannot acces the RaQ from where I am now). There 
was something about a undeclared function. I also got a load of warnings before 
that error...
The same problem occures with package 2.5.1.
 
But the interesting part is that the very same package DOES 
compile on a standard RedHat 7.1 firewall box.
That box has a newer version of gcc, so maybe that is the 
reason? The RaQ1 has version 2.7.something, and the RH 7.1 box has 2.9... What 
version of gcc does Rsync need?
 
I cannot compile Rsync on the RH 7.1 box and copy those files, 
because the RaQ 1 is a mipsel-unknown-linux-gnu host with very different 
hardware than that of the RH 7.1 box.
 
Oh yeah, I also thought of missing header files, but I don't 
think that is the problem, because I don't have problems compiling other 
programs. Above all, there is a directory with include files in /usr/src/linux 
(and the source is also available...)
 
Can anyone give me advise on how I can get Rsync to compile 
correctly? Thanks in advance,
 
   
Greetz -- Jurrie   
[EMAIL PROTECTED]
 
PS: It appears the search archives option is broken, please 
fix this, as it's a very handy option!