On 8 Feb, Dave Dykstra wrote:
>
> The problem with full pathname symlinks and "use chroot = no" is that it
> can let somebody affect things outside of the module. For example,
> somebody could first upload a symlink to a directory outside of the module
> and then write into it. I implemented t
On 8 Feb, [EMAIL PROTECTED] wrote:
> It may be that you can fix your problem without modifying rsync or getting root
>access to do chroot, simply by making your symlinks relative in the source.
> If /module/dir/link points to /othermodule/otherdir, perhaps you could point it to
>../../othermod
ng to other files
> within the root path, and leading slashes are removed from
> absolute paths.
>
> - Dave Dykstra
--
Diab Jerius Harvard-Smithsonian Center for Astrophysics
60 Garden St, MS 70, Cambridge MA 02138 USA
[EMAIL PROTECTED] vox: 617 496 7575 fax: 617 495 7356
Here's a mystery (to me at least!):
I've got a symbolic link on the source disk which looks like this:
> ls -l /proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp
[...]
/proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp ->
/proj/axaf/Simul/bin/mips4_r10k-IRIX-6/spatquant_bp-D2304
my rsyn
On 5 Feb, Dave Dykstra wrote:
> -g uses chown. You need to be the owner of a file to change the group.
> Were the files already there owned by somebody else?
aha. yup, on the server side they're owned by a variety of users. This
is a really messy interleaved mirror that I'm doing; some stuff g
I'm uploading files to an rsync server using the options
-vrlptgx
I'm getting tons of chown errors on the server side for directories.
Now, if it was *supposed* to be chown'ing stuff, I expect the errors,
as I'm not running the server as root, and there is a different owner
on the server sid
