[Digikam-devel] Bug#673161: Starting mysqld in a chroot
    Arnold Metselaar 
    arnold.metsel at gmail.com
       
    Fri May 18 07:21:38 BST 2012
    
    
  
Hi, 
I was mistaken in my previous message.  Generating a decent /etc/mtab with the line
grep "${CHROOT_PATH}" /etc/mtab | sed -e "s:${CHROOT_PATH}/\?:/:" >"${CHROOT_PATH}/etc/mtab"
in /etc/schroot/setup.d/99mini-buildd helped get rid of warnings from df,  
but mysqld was trying to start without it as well.
Mysqld tries to bind to a port at start-up, and fails when another mysqld outside the chroot is already
bound to that port. When mysqld is not running in the host machine, it starts in a chroot just fine. 
It should also work when mysqld in the host is listening on a non-standard port.
Regards,
Arnold
    
    
More information about the Digikam-devel
mailing list