Bug #18018 PID file problem -> wrong use of "kill"
Submitted: 7 Mar 2006 11:28 Modified: 29 May 2006 11:22
Reporter: Joerg Bruehe Email Updates:
Status: Duplicate Impact on me:
None 
Category:Instance Manager Severity:S3 (Non-critical)
Version:5.0.19 OS:Other (OpenBSD)
Assigned to: Assigned Account CPU Architecture:Any

[7 Mar 2006 11:28] Joerg Bruehe
Description:
Release build of 5.0.19, test failure on "granny" (OpenBSD 3.9):

im_daemon_life_cycle           [ fail ]

Errors are (from PATH/mysqltest-time) :
cat: /home/mysqldev/granny/test/mysql-pro-5.0.19-openbsd3.9-i386/mysql-test/var/run/im.pid: No such file or directory
Usage: kill [ -s signame | -signum | -signame ] {pid|job}...
       kill -l [exit_status]
mysqltest: Result length mismatch
(the last lines may be the most important ones)
Below are the diffs between actual and expected results:
-------------------------------------------------------
*** r/im_daemon_life_cycle.result
--- r/im_daemon_life_cycle.reject
***************
*** 4,7
  mysqld2       offline
  Killing the process...
  Sleeping...
! Success: the process was restarted.
--- 4,7
  mysqld2       offline
  Killing the process...
  Sleeping...
! Error: the process was killed.
-------------------------------------------------------

How to repeat:
Test suite failure.

Suggested fix:
Do not call "kill" unless a (syntactically) valid PID was determined.
[29 May 2006 11:22] Alexander Nozdrin
This is a duplicate of BUG#18023.