Running a process confined and chrooting are typically two different,
mutually-exclusive solutions to the same problem.
The apparmor profile contains mysqld in a similar way that the
traditional chrooting does. There is no reason to chroot mysqld on
Ubuntu if you are using the AppArmor profile.
hmmm, sorry for my incomprehension, but I don't understand why MySQL 5.0 works
with apparmor in chroot, and MySQL 5.1 does not?
Only this is my problem, everything else is clear for me.
Thank you:
a.
--
mysql-server-5.1 can't chroot
https://bugs.launchpad.net/bugs/434915
You received this
** Package changed: ubuntu = mysql-dfsg-5.1 (Ubuntu)
--
mysql-server-5.1 can't chroot
https://bugs.launchpad.net/bugs/434915
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.1 in ubuntu.
--
Ubuntu-server-bugs mailing list
Thank you for taking the time to report this issue and helping to make
Ubuntu better. We appreciate the difficulties you are facing - why are
you running mysqld in a chroot?
** Changed in: mysql-dfsg-5.1 (Ubuntu)
Importance: Undecided = Low
** Changed in: mysql-dfsg-5.1 (Ubuntu)
