http://qa.mandrakesoft.com/show_bug.cgi?id=6034
------- Additional Comments From [EMAIL PROTECTED] 2003-01-10 14:22 ------- Created an attachment (id=907) --> (http://qa.mandrakesoft.com/attachment.cgi?id=907&action=view) example service 'dauerping' for reproducing the bug Try this: cp dauerping /etc/init.d service dauerping start service dauerping status will give: dauerping dead but pid file exists By using 'ps' you may verify that the service in reallity is running. -- Configure bugmail: http://qa.mandrakesoft.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------- Reminder: ------- assigned_to: [EMAIL PROTECTED] status: UNCONFIRMED creation_date: description: In /etc/init.d/functions the function named 'status' has a minor bug: If the process-name and the service-name differ, 'status()' will always report "is dead, but pid file exists". This is the case even if the service is running properly and the contetn of the pid file is correct. This bug reasons in the assumption of 'status()' that servicename and processname are always the same. If they differ, 'pidof' does not deliver a value and 'status()' thinks it is not running. A good reason for processname and servicename differing: I have a service called 'dauerping' (endless-ping) which just start an endless ping. The process-name will be just 'ping', which is not quite usefull for beeing used for 'pidof': 'pidof ping' would deliver a result even if the 'dauerping' of the service is not running -- just because 'ping' is used very often. The patch enclosed solves this problem: read the pid-file's content and ask 'ps' about the status of the process. If requested, I may supply the 'dauerping' service for you to reproduce the problem on any system.
