FYI (but take everything here with a grain of salt, I'm not sure)
The reason mysql ignored SIGTSTP was that an ancient apple OS was
sending that signal randomly.
If that's true it should be safe by now to re-enable the functionality
in drizzle.
Francesco
Il 01/05/2012 22:06, Henrik Ingo ha scritto:
There was a branch / merge request that fixed it, and you commented
something along the lines of "this is the same as mysqld does" and
didn't approve it. The branch was then deleted by its author so I
can't find it anymore.
We really just would like to know whether we can fix the bug (e.g make
Ctrl-C be the key to kill drizzled, and perhaps Ctrl-Z for stopping)
or just forget it. If you think current behavior is correct, then I
would be curious about an explanation beyond "this is how MySQL always
did it" would be interesting, since generally Drizzle likes to break
from past MySQL habits.
henrik
On Tue, May 1, 2012 at 4:43 AM, Brian Aker<br...@tangent.org> wrote:
Hi!
Where did I comment that it was invalid?
Cheers,
-Brian
On Apr 27, 2012, at 11:50 AM, Henrik Ingo wrote:
Brian
You seem to think that this bug is invalid, and current behavior is
correct. Could you make a comment on the bug (and close it, if that's
what you feel).
https://bugs.launchpad.net/drizzle/+bug/739702
henrik
--
henrik.i...@avoinelama.fi
+358-40-8211286 skype: henrik.ingo irc: hingo
www.openlife.cc
My LinkedIn profile: http://www.linkedin.com/profile/view?id=9522559
_______________________________________________
Mailing list: https://launchpad.net/~drizzle-discuss
Post to : drizzle-discuss@lists.launchpad.net
Unsubscribe : https://launchpad.net/~drizzle-discuss
More help : https://help.launchpad.net/ListHelp
