Hi, On Fri, Jan 16, 2009 at 06:09:59PM +0100, Raoul Bhatia [IPAX] wrote: > unfortunatly, in a more complex environment where one does not rely on > /etc/mysql/* for configuration (e.g. in an linux-ha/pacemaker > environment), the start is likely to fail thus leaving the package - and > thus the whole package system - in the "Failed-cfg"-state: [...] > Is it possible to make the mysqld start optional - e.g. preinst checks > if mysqld is/was running and "tell" postinst what to (not) start? > > Or maybe it is possilbe to continue even if the mysqld start fails?
On a related note there was a request [1] from a Kubuntu developer about splitting the mysql-server package into two packages: one that would provide the mysqld binary (ex: mysql-server-common-5.0) and one that would provide the init script (ex: mysql-server-5.0). Samba and apache2 are two packages that provide such an infrastructure. Having a mysql-server-common-5.0 package would solve the problem stated above. [1]: https://lists.ubuntu.com/archives/ubuntu-server/2009-January/002569.html -- Mathias Gug Ubuntu Developer http://www.ubuntu.com -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
