Hello Sean

On 2005-03-01 sean finney wrote:
> On Wed, Mar 02, 2005 at 12:24:28AM +0100, Christian Hammers wrote:
> > No, it's mainly created by the last version's prerm script if
> > "/usr/bin/mysqladmin --defaults-extra-file=/etc/mysql/debian.cnf ping"
> > gives some output which is "mysqld alive" if the server is currently
> > running.
> 
> this seems kind of dodgy, and somewhat stretching what the fhs
> should allow...

Why do you think? The FHS governs mainly the locations of files as far as
I know and even our Debian policy does not mandate that I immediately
start a server upon upgrading if it was not running before.

To clarify, this flag-thingy is *only* used when installing or upgrading
the packages. On normal system boots the init scripts are consulted.


> > > +if [ "$1" = "install" -o "$1" = "upgrade" ]; then
> > No, that would be the same as unconditionally start the 
> > server at the end of postinst but the intend was to preserve
> > the running state before the upgrade or start the server if it is
> > a fresh install.
> 
> shouldn't invoke-rc.d take care of determining whether or not
> to start mysql?

That's the alternative. The current system is just one step cleverer -
if it would only work as it used to :-(


> > It would be very helpful to get the output of the *complete* upgrade
> > process inclusive the prerm when running with "set -v -x" or with
> > "export DEBIAN_SCRIPT_DEBUG=1".
> 
> i was going to volunteer myself, but am unable to reproduce it
> by upgrading from 4.0 to 4.1.

Too bad :-( It's hard to believe that 5-6 people really had no server
running although they believed they had.

I wait 1-2 days more if somebody has a clue and then I revert to simply
calling "invoke-rc.d mysql-server start" at the end of postscript by
reenabling the debhelper scripts there.

(BTW: Sean: I've just uploaded a new version of 4.0 but that did not contain
any relevant changes it is just to test if the new dpatch system I used for
svn-buildpackage works for the autobuilders)

bye,

-christian-


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to