Re: rsync wont run w/o disabling chroot in config.
Brought to you by:
xystrus
From: Paul B. <Pau...@va...> - 2006-02-04 22:55:28
|
Gian G. Spicuzza wrote: > Hi Paul, > > Yes I do have allowrsync in my rssh.conf > > --server appears on the server side when it is receiving files via rsync. > > The actual command on the client side was: > > rsync -e ssh -avz openssh-4.0p1-i486-1.tgz > rssh@192.168.1.10:/home/rssh/data > > (I think it tried it with both /data/jail/home/rssh/data and > /home/rssh/data -- no luck though) > (I did use a script to get my libraries copied over, tomorrow morning I > will try to build > another chroot jail strictly from the CHROOT files howto and see how > that works) > > Thanks! > > Gian My guess is you would also need allowscp since you're using ssh. I've never tried this option. I normally either use unsecured rsync or scp. > rsync -e ssh -avz openssh-4.0p1-i486-1.tgz > rssh@192.168.1.10:/home/rssh/data With a chrootpath of /data/jail will look for openssh-4.0p1-i486-1.tgz in your current dirctory on your local machine and would try to put it in /data/jail/home/rssh/data/ on the remote machine. I generally just use rsync to get a local copy of Linux update RPM's, so I don't know if it would try creating subdirectories if they don't exist. Chroot jails can be tricky, so it's always advisable to strictly follow the instructions to create the jail. Leaving anything out will cause problems. Paul Boniol |