Summary: | dev-db/mysql init script does not handle chroot | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Cory Visi (RETIRED) <merlin> |
Component: | New packages | Assignee: | Gentoo Linux MySQL bugs team <mysql-bugs> |
Status: | RESOLVED OBSOLETE | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
mysql-5.0.26-r1.ebuild.patch
mysql.rc6.patch mysql.conf.d.patch |
Description
Cory Visi (RETIRED)
2006-10-25 07:32:56 UTC
Created attachment 100458 [details, diff]
mysql-5.0.26-r1.ebuild.patch
Created attachment 100459 [details, diff]
mysql.rc6.patch
Created attachment 100460 [details, diff]
mysql.conf.d.patch
I should also state that this chroot environment is created by simply placing: chroot = /home/mysql under the mysqld section of my.cnf. I also want to be clear on this point: I am making this bug "normal" severity, because if you do use the my.cnf line mentioned above, Gentoo's init script thoroughly breaks. Yeah, we never advertised it does handle/support chroot, why are you surprised? :) Re-marking as enhancement, as Jakub stated it was never actually intended to work with chroot support... We'll ponder this and maybe add it, if you could update the patches to cleanly apply to the latest init.d/conf.d scripts, now found in dev-db/mysql-init-scripts, that would be greatly appreciated! Best regards, CHTEKK. I'm trying to run mysql-5.0.38 under chroot.. Without your patches "/etc/init.d/mysql start" was giving me this: ---------- * Caching service dependencies ... [ ok ] * Remounting root filesystem read-only ... mount: / not mounted already, or bad option [ !! ] * Checking root filesystem ... ext2fs_check_if_mount: No such file or directory while determining whether /dev/ROOT is mounted. fsck.ext3: No such file or directory while trying to open /dev/ROOT /dev/ROOT: The superblock could not be read or does not describe a correct ext2 filesystem. If the device is valid and it really contains an ext2 filesystem (and not swap or ufs or something else), then the superblock is corrupt, and you might try running e2fsck with an alternate superblock: e2fsck -b 8193 <device> ... Press Ctrl+D to debug / reboot, e.t.c.... --------- After all patches there's no halts now.. but: mysql doesnt launch finally: "mysqld is already starting", and 'ps ax|grep mysql' shows me startup script is running.. can u check/release your patches for the latest mysql? Please respin against mysql-init-scripts-2.0_pre1 No response from user for 2 years. |