Bug #67052 | safe_process.cc/safe_process.pl should not kill mysqld on SIGSTOP/SIGCONT | ||
---|---|---|---|
Submitted: | 2 Oct 2012 11:18 | Modified: | 22 Apr 2013 16:52 |
Reporter: | Laurynas Biveinis (OCA) | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Tests: System | Severity: | S3 (Non-critical) |
Version: | 5.1, 5.5, 5.7.0, 5.5.29, 5.1.67 | OS: | Any |
Assigned to: | CPU Architecture: | Any | |
Tags: | Contribution, safe_process |
[2 Oct 2012 11:18]
Laurynas Biveinis
[12 Oct 2012 19:18]
Sveta Smirnova
Thank you for the report. Verified as described.
[7 Feb 2013 5:54]
Laurynas Biveinis
Fixed in 5.1 revno 3871. Sadly the commit does not mention "67052" in addition to the internal bug #. Bug #14757120 - SAFE_PROCESS.CC/SAFE_PROCESS.PL SHOULD NOT KILL MYSQLD ON SIGSTOP/SIGCONT This bug may be closed as fixed now.
[20 Apr 2013 12:56]
Laurynas Biveinis
Any news on closing this bug? Thanks.
[22 Apr 2013 10:43]
Sayantan Dutta
its been fixed!
[22 Apr 2013 16:52]
Laurynas Biveinis
The reason I asked, instead of closing this bug myself, which I can do as the submitter, is because Oracle usually adds the release notes entries upon closing.
[24 Apr 2013 15:25]
Paul DuBois
Changes to test suite. No changelog entry needed.