[Bug 326768] Re: mysqld_safe thinks mysqld has crashed when it hasn't
MarcRandolph
mrand at pobox.com
Tue May 12 07:54:17 BST 2009
I'm not sure if I'm late to the party or not here... but on the off
chance that it would be helpful, I threw together a program to print out
the source process ID for a SIGHUP signal. I have attached the source
to this bug. Very simple to use... in this case:
1. mv mysqld_safe mysqld_safe_real
2. gcc sig_src.c -o mysqld_safe
3. Launch programs/services that cause crash
4. Watch stderr output, wherever that happens to be going. This could be modified to log to a file.
** Attachment added: "Determine the process ID of SIGHUP source"
http://launchpadlibrarian.net/26623864/sig_src.c
--
mysqld_safe thinks mysqld has crashed when it hasn't
https://bugs.launchpad.net/bugs/326768
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to mysql-dfsg-5.0 in ubuntu.
More information about the Ubuntu-server-bugs
mailing list