On Jan 18, 2010, at 16:24, Scott Haneda wrote:

> On Jan 18, 2010, at 1:55 PM, Ryan Schmidt wrote:
> 
>> On Jan 18, 2010, at 04:41, Scott Haneda wrote:
>> 
>>> You can unload Apache two ways:
>>> 
>>> sudo port unload apache2
>>> - or -
>>> sudo launchctl unload -w /Library/LaunchDaemons/org.macports.apache2.plist
>>> 
>>> That should stop Apache from that point forward. The first method will only 
>>> stop Apache for that login session. The second will stop Apache even beyond 
>>> a reboot.
>> 
>> Not true; both methods are completely synonymous. One is just easier to type 
>> and remember.
> 
> So port load/unload toggles the -w aspect of launchctl? I was not aware of 
> this. Good to know.

Yes:

http://trac.macports.org/browser/trunk/base/src/port1.0/portload.tcl?rev=60774#L60


>>> Either way, from there, delete the plist and you are done.
>>> 
>>> sudo rm /Library/LaunchDaemons/org.macports.apache2.plist
>> 
>> There's no reason to delete the plist. Just deactivate it as above and the 
>> server won't run anymore.
> 
> The OP mentioned they accidentally forgot to remove the startup item variant.
> 
> Had the startup item variant not been installed, does that mean the plist is 
> still written, just with the disabled key set?

Well, they said they forgot to use the no_startupitem variant. But I see no 
reason for the variant to exist and think we should remove it. Recall prior 
discussion on this, e.g. my last paragraph in this email:

http://lists.macosforge.org/pipermail/macports-dev/2010-January/010976.html


_______________________________________________
macports-users mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-users

Reply via email to