Jochen Küpper <[EMAIL PROTECTED]> writes: >I always wondered why my apache would not start at boot-time... Now I >updgraded to MacPorts apache2 version 2.2.6 and take a quick look >into it. Apparently one has to edit > /opt/local/etc/LaunchDaemons/org.macports.apache2/ >org.macports.apache2.plist >and change the Disabled key to false? > <key>Disabled</key><false/> > >Is this true? If so, this should be documented in the info-message >given upon installation of apache2 via MacPorts: > >########################################################### ># A startup item has been generated that will aid in ># starting apache2 with launchd. It is disabled ># by default. Execute the following command to start it, ># and to cause it to launch at startup: ># ># sudo launchctl load -w /Library/LaunchDaemons/ >org.macports.apache2.plist >########################################################### > >This message indicates, launchctl would take care of that stuff. It >doesn't, at least not for me. >If, however, the user has to do this manually, it should be said at >that point. > >If I am overlooking something, I am happy to learn about it;)
Hi Jochen, sudo launchctl load -w /Library/LaunchDaemons/org.macports.apache2.plist is intended to remove the "Disabled" tag, and always has for me. And unload will place it there again. I'm not sure why it wouln't do that for you though. Mark _______________________________________________ macports-users mailing list macports-users@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-users
