[MacPorts] #33436: Squid3 fails to start with launchctl start, but does start with launchctl stop

[MacPorts]

#33436: Squid3 fails to start with launchctl start, but does start with launchctl
stop
--------------------------------------+-------------------------------------
 Reporter:  dan+macports@…            |       Owner:  jmr@…           
     Type:  defect                    |      Status:  new             
 Priority:  Normal                    |   Milestone:                  
Component:  ports                     |     Version:  2.0.3           
 Keywords:                            |        Port:  squid3          
--------------------------------------+-------------------------------------

Comment(by dan+macports@…):

 Replying to [comment:4 jmr@…]:
 | So the summary is wrong and stop doesn't actually start the daemon?

 The summary is correct. "launchctl stop" does start squid, because it
 kills
 daemondo and on restart (of daemondo) squid is started.

 There are 3 levels of daemons to start involved here:
     launchd
     daemondo
     squid

 The one which I noticed the wrong behaviour was launchd.
 The one which is the real culprit is the shell script called by daemondo:
     Squid.wrapper

 I'm working on a fix and testing it.

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