ports/170980: startup script bug

[Nicolas Szalay]

>Number:         170980
>Category:       ports
>Synopsis:       startup script bug
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-ports-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Aug 24 07:10:03 UTC 2012
>Closed-Date:
>Last-Modified:
>Originator:     Nicolas Szalay
>Release:        9.0-RELEASE
>Organization:
Fotolia
>Environment:
FreeBSD eqx-admin1.fotolia.loc 9.0-RELEASE-p3 FreeBSD 9.0-RELEASE-p3 #0: Tue Jun 12 02:52:29 UTC 2012     root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64

>Description:
When using freebsd 9 & mcollective 2.1, the startup script does not evaluate correctly the status of the daemon :

[eqx-admin1:~] sudo /usr/local/etc/rc.d/mcollectived start 
Starting mcollectived.
[eqx-admin1:~] sudo /usr/local/etc/rc.d/mcollectived status
mcollectived is not running.

when checking pid file, and pid list (and functionality of the daemon), it's OK.

I think it's due to the procname directive in the rc.d script. It is set to "ruby", while process list shows :

root        305   0.0  0.0 215936  19292  ??  S     6:48AM     0:00.51 /usr/local/bin/ruby19 /usr/local/sbin/mcollectived .....

setting procname to "/usr/local/bin/ruby19" makes it happy.

When running a config management tool like chef, it spawns hundreds of process and crashes the machine.
>How-To-Repeat:
launch rc.d script
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted: