When a user logs in, what would prevent them from accessing their files in /var/www/home/wherever by just using the cd command to change to that directory? Just make sure permissions on whatever they need to access in /var/www/home/wherever are such that the users can change files and Apache can read files. If you want to make it a little easier for the users to find their place in /var/www/home/wherever you could create a symlink within their home directory that points to that location: "ln -s /var/www/home/user ~user/webfiles"
On Friday 19 May 2006 14:37, you wrote: >Hi, > >I have a new server (2.66Ghz Core Duo) with a spangly new LSI >MegaRaid card (disable pcibios made it boot happily using bsd.mp), >and once we'd found the broken stick of RAM everything's happy (dmesg >at end) > >I have a systems question, relating to apache. I would like to run >apache chrooted, but users need access to their both home directories >in /home, and their web directory in /var/www/home/wherever. Ideally >I'd like to do this under one login per user, but I can't think how >to setup the system so they can access /home, and their chrooted area >with one account. > >I don't want to put the entire /home partition into the chroot, that >leaves everybody's files vulnerable if apache/php gets haxored. I >could just keep each users websites folder in the chroot, but then >sftpd or ftpd (both chrooted) won't be able to see them either. > >I can't think of a way round this, to have chrooted access, with >files in separate locations, accessible under one login. Does >anybody have any suggestions? ------------------------------------------------------------------------ Dan Ramaley Dial Center 118, Drake University Network Programmer/Analyst 2407 Carpenter Ave +1 515 271-4540 Des Moines IA 50311 USA
