[MacPorts] #27578: mpd: killing daemon with "launchctl -w unload ..." has no visible effect (kills wrong process)

[MacPorts]

#27578: mpd: killing daemon with "launchctl -w unload ..." has no visible effect
(kills wrong process)
--------------------------+-------------------------------------------------
 Reporter:  greg@…        |       Owner:  milosh@…           
     Type:  defect        |      Status:  new                
 Priority:  Normal        |   Milestone:                     
Component:  ports         |     Version:  1.9.1              
 Keywords:                |        Port:  mpd                
--------------------------+-------------------------------------------------

Comment(by greg@…):

 Forgot to mention I'm on OS X 10.4.11.  Perhaps launchd behaved a little
 differently back in ye olden days of Tiger.  (This is on a G4, and I've
 tried running Leopard.  Too slow.  Tiger is just fine on this machine.)

 Anyways, I "fixed" this for now by modifying the launchd properties file
 for mpd.  Specifically, I made it a lot simpler, completely avoiding
 mpd.wrapper and daemondo:
 {{{
         <key>ProgramArguments</key>
         <array>
                 <string>/opt/local/bin/mpd</string>
                 <string>--no-daemon</string>
                 <string>/opt/local/etc/mpd.conf</string>
         </array>
 }}}

 Now launchd and mpd interact as I expected: "load -w" starts mpd and
 "unload -w" kills it.

 Obviously, this is a short-term kludge: I assume it will be clobbered by
 the next upgrade of mpd.

-- 
Ticket URL: <https://trac.macports.org/ticket/27578#comment:3>
MacPorts <http://www.macports.org/>
Ports system for Mac OS