i can trigger this problem on my laptop which is *not* running mythbackend by simply issuing 'sudo killall -HUP mysqld_safe'. So it's not related to MythTV.
In fact, if you issue 'mysqladmin refresh' as done by mysqld_safe when it catches a SIGHUP, mysqld will *not* crash. See Mario's explanation why the patch is broken.
How to break it:
sudo killall -HUP mysqld_safe
Expected behavior:
* 'mysqladmin refresh' is run
OR
* nothing happens, as intended by upstream
Mathias,
i can trigger this problem on my laptop which is *not* running mythbackend by simply issuing 'sudo killall -HUP mysqld_safe'. So it's not related to MythTV.
In fact, if you issue 'mysqladmin refresh' as done by mysqld_safe when it catches a SIGHUP, mysqld will *not* crash. See Mario's explanation why the patch is broken.
How to break it:
sudo killall -HUP mysqld_safe
Expected behavior:
* 'mysqladmin refresh' is run
OR
* nothing happens, as intended by upstream
Resulting behavior:
* mysqld is restarted