> Generally I don't like substituting binaries and libraries while the > program is still running. Also, things like upgrading the mysql privilege > tables or changing the config files can be done during the postinst > phase in an upgrade. It's safer to stop the server during that time.
Sorry, but this is really admins decision. I'm very confused how anybody could allow mysql to stop when I'm upgrading. Linux is very stable system and one of greatest think is that I can do things like upgrading from woody to sarge nearly without downtime! So, please, provide user with debconf question if he wants to shutd down the server during upgrade or if not. If there is need for upgrading mysql privilege tables, so ask user if he wants (he can do this later himself). Config file can be changed without any problem. And upgrading mysql privilege tables is needed between major versions but not between minor fixes... And one important thing. There is no need to shutdown server twice which enlarge downtime :( > As admin better use "apt-get -u upgrade", ctrl-c and then upgrade > important > pieces in separated steps to shorten the downtime. but it is still very long time. I can do mysql restart in one or two seconds but stop it, make some things, stop it and start it is almost ten seconds. And it is very very bad for production server. > > I leave the bug open as reference but tag it "wontfix". I'm kindly asking you to change your opinion. This is big problem for us and I think that for many others. Thanks Ondřej Kudlík
