rsync - Jun 2004 - [Fwd: Re: rsync server complaining about vanishing files while they are not.]

Greetings.


   Yep, I have set "use chroot = no" for the module and it works.  The
symlinks
I have are created automatically by a tool and are absolute.  But since
"use
chroot = no" handles well absolute links from root/, the transfer works A1.

   Thanks for your input, Wayne.


Best regards,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc.     Open source:
http://www.deragon.biz        http://facil.qc.ca (Promotion du libre)
mailto://hans@deragon.biz     http://autopoweroff.sourceforge.net (Logiciel)

-------- Original Message --------

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wayne Davison wrote:
> On Mon, Jun 07, 2004 at 04:30:56PM -0400, Hans Deragon wrote:
>
>>As seen above, they are absolute, but there is no NFS mounting involved
>>here.
>
>
> You're probably running the rsync daemon with "chroot = yes"
then.  If
> the files are inside the chroot area, you can switch the symlinks to be
> relative and they will work.  If they are outside the chroot area,
> you'll have to turn chroot off.
>
> ..wayne..
Greetings again.


  I am at home now, so I will check this tomorrow (I am not the one who
configured rsyncd.conf).  But if you are right, would it be possible to have
rsync spit out a different error message for this circumstance?  A
"vanishing"
message does not describe the problem.  If the link exist, could rsync verify
if the symlink is absolute and if chroot is on?  If both conditions are true,
a more appropriate message could be printed.  A message which would not cause
a newbie like me to post. :)


Thanks for the quick support.
Hans Deragon
- --
Consultant en informatique/Software Consultant
Deragon Informatique inc.     Open source:
http://www.deragon.biz        http://facil.qc.ca (Promotion du libre)
mailto://hans@deragon.biz     http://autopoweroff.sourceforge.net (Logiciel)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAxRdHOvOyYOyQFhwRAkB+AJ9RtwU1Q0/GyZFq3StPn7UKSepyswCbBzR8
WFlPqDsVU1Y1OYxLXl2sP8o=aABz
-----END PGP SIGNATURE-----

Hans:  Unless your server is in a completely trusted network, I'd suggest 
you put down some include/exclude rules for that module, because people 
can poke about anywhere they want.
[module]
path = /only/directory/you/want/to/give/them
use chroot = no

user does
rsync server::module/../../../../../../../etc/security/passwd .

Permissions (don't put "uid = 0" in the rsyncd.conf) can prevent
that one,
but
rsync -a server::module/../../../../../../.. .
is probably something you don't want.

Tim Conway
Unix System Administration
Contractor - IBM Global Services
desk:3032734776
conway@us.ibm.com




   Yep, I have set "use chroot = no" for the module and it works.  The
symlinks 
I have are created automatically by a tool and are absolute.  But since 
"use 
chroot = no" handles well absolute links from root/, the transfer works 
A1.

   Thanks for your input, Wayne.