Dave, can you explain to me what exactly unsafe_symlink is meant to
do? I can see broadly that it's meant to prevent symlinks pointing
out of "the directory being copied", but when not using path= and a
daemon it's not clear what directory that refers to.
Also, I don't understand this line:
>
Hi
I want to exclude some files from a Raid so can
anybody explain me how can i do that
Regards
Rizvi inamdar
On 5 Apr 2002, Mark Santcroos <[EMAIL PROTECTED]> wrote:
> While digging through the code it was sometimes unclear to me what the
> particular piece of code does. I found the number of comments very low.
> How about that we put some more description in the code to make it easier
> for everyone?
Thanks for the report. I think there is still a problem in 2.5.5, but
I'm not sure if it is working-as-designed or not.
The problem seems to lie in flist.c, perhaps in the topsrcname
variable. I'm not quite sure what this does.
I checked in your script as unsafe-links.test.
--
Martin
--
On 21 Mar 2002, Dave Dykstra <[EMAIL PROTECTED]> wrote:
> > > I guess that makes sense; I can't think of another easy to do what you want
> > > to do. Pretty obscure case though.
> >
> > Obscure now, but I expect not forever.
> >
> > If you consider it desirable for rsync to be able to do this
Martin Pool writes:
> Hi Richard.
>
> I think the problem you are experiencing is caused by a known bug in
> 2.5.4. Could you please let me know if 2.5.5rc1 (or CVS HEAD) fixes
> the problem?
Apologies, but I didn't have time to play with this until today. I've
just grabbed 2.5.5 and the proble
