Hi all, I'm wanting to set up mysql to run in a chroot jail. I saw the command line option --chroot and tried this which seemed to work (well mysql ran anyway). I added this to the startup script (running redhat 7.0) in /etc/rc.d/init.d/mysql so that it would use this option (and because I need to server to start automatically after a reboot) and thought I'd try it out. I created a new database, but it appeared outside the chroot jail in /var/lib/mysql which is what the datadir is set to but I thought that if running in a chroot jail then it should go to the one inside the chroot not one outside. I then set the chroot up by copying all of the bits from the rpm distribution into the chroot environment, altered the startup script and tried to run it, but it complains about not having touch, sed etc (which I haven't put in the chroot - the less the better). Now, it might not be a problem to copy all of the relevant bits into the chroot environment, but this little experience has got me wondering what is actually happening when I use the --chroot command line option to start the mysql server? At what level are things in the chroot (and what bits are not), or is it more likely that my setup is not correct and that when using the --chroot command switch it isn't actually running properly? I'm running Red Hat Linux v 7.0, MySQL 3.23.31 installed from rpms, any help would be much appreciated. cheers, noel --------------------------------------------------------------------- Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail <[EMAIL PROTECTED]> To unsubscribe, e-mail <[EMAIL PROTECTED]> Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
