Jeremy:
Looks like I might have to eat my words a little. Not entirely on the running
of MySQL in a jail, but, perhaps that too, in time.
The application started as a knowledge-base, billing application.
The piece I'm concerned with now involves an implementation using
.profile/.bash_profile m
On Wednesday 06 June 2001 08:53, dariofg wrote:
> Hello,
>
> I'm trying to run mysql in a chroot jail, but the server
> errors out. I've modified safe_mysqld so it would call
> MySQL with the following command:
>
> nice --5 nohup /usr/local/mysql/libexec/mysqld --
> basedir=/ --datadir=/var --use
On Thu, Jun 07, 2001 at 04:56:12PM -0700, Kyle Hayes wrote:
>
> One of the problems I had when running MySQL in a chroot jail was
> that the /etc/passwd, /etc/shadow etc. had to be correct in the
> jail. However, I don't think I am running it in the same
> configuration that you use. See below.
On Wed, Jun 06, 2001 at 03:04:23PM -0700, Van wrote:
>
> I've dealt with jails and question the wisdom of using them.
>
> There are better ways to do this, and, your application will suffer
> tremendous portability issues which will probably make it useless
> for most people.
>
> If you're the
dariofg wrote:
>
> Hello,
>
> I'm trying to run mysql in a chroot jail, but the server
> errors out. I've modified safe_mysqld so it would call
> MySQL with the following command:
>
> nice --5 nohup /usr/local/mysql/libexec/mysqld --
> basedir=/ --datadir=/var --user=mysql --pid-
> file=/var/h
Hello,
I'm trying to run mysql in a chroot jail, but the server
errors out. I've modified safe_mysqld so it would call
MySQL with the following command:
nice --5 nohup /usr/local/mysql/libexec/mysqld --
basedir=/ --datadir=/var --user=mysql --pid-
file=/var/hayek.pid --skip-locking --
chroot=/u
