- #MAC OS X APACHE EXECUTE FOR MAC#
- #MAC OS X APACHE EXECUTE 64 BIT#
- #MAC OS X APACHE EXECUTE UPDATE#
- #MAC OS X APACHE EXECUTE DRIVER#
- #MAC OS X APACHE EXECUTE 32 BIT#
#MAC OS X APACHE EXECUTE FOR MAC#
There are some drawbacks to OpenOffice for Mac of course. The six components OpenOffice for Mac comes with are Write, Calc (spreadsheets), Impress (presentations), Draw, Base (database management) and Formula (mathematical application). It may not be quite as polished as Microsoft Office but considering you get all this for nothing, you really can't complain.
#MAC OS X APACHE EXECUTE UPDATE#
#MAC OS X APACHE EXECUTE 32 BIT#
Edit it (and I would probably use Lingon) to start apache in 32 bit mode.Back up /System/Library/LaunchDaemons/, perhaps to another folder.In /var/log/apache2/error.log, it did show that the application was shut down and started up, but I don't know if it was direct or not. I opened Console while toggling the switch. It starts apache directly and does not use launchctl.It uses /System/Library/LaunchDaemons (and if you backed this up and overrode it, you'd get the results you seek).Why does apache start up differently from System Preferences? I have two guesses. Which sure looks right (although I'm unsure if sudo is required for the second one). Sudo launchctl load /Library/LaunchDaemons/ The site you referenced listed the commands to unschedule the original task and schedule in your replacement as: sudo launchctl unload /System/Library/LaunchDaemons/ You can edit the file, or, when using the launchctl load or unload command, you can make use of the -W flag to override the current setting and write it back to disk. Note that in the configuration files, there is a key that states if the job is disabled. Launchctl will also let you schedule/unschedule tasks. I believe that root sees the tasks that are scheduled from /System/Library/LaunchDaemons and LaunchAgents, and that the user sees ones scheduled from /Library/LaunchDaemons and LaunchAgents. Note that you get different results if you do it as a user than if you do it as root. To see which tasks are scheduled, you can run: launchctl list To see a list of all services, but unfortunately, the data does not go to stdout, and you can't pipe it.]Īnother useful tool to help you figure this out is launchctl. [but replace '' in the command with whatever you've configured it to be. Service -test-if-configured-on & echo "On" || echo "Off" To check if it is available and on, you can do the following: service -test-if-available & echo "Available" || echo "Not available"
You may want to change the name of your service in the plist configuration file.
Be sure to look at the expert mode, especially for looking at an existing file, and note that under the help menu, you can access all relevant man pages. I know when I'm mucking with services, I really like to use Lingon (even though it is no longer actively developed.) It gives a good idea of which tasks are scheduled, it can help for checking that your task set to be active or not, and I believe it'll check the consistency of your plist file (although, since you started from an existing one, it is likely to be good), and it is really nice for editing a launchd plist file. I believe that you can verify the parameters actually passed to the application by running: ps auxw | grep http Or am I just doing things in a plain crazy manner? Should I remove/rename the /System/Library/LaunchDaemons/ file, or is there a better way of doing things? Why am I seeing that starting Apache via the System Preferences result in different behaviour than via a reboot?
#MAC OS X APACHE EXECUTE 64 BIT#
However if I open up the System Preferences->Sharing and restart Apache by Unchecking and rechecking the "Web Sharing" option, Apache starts up in 64 bit mode (as seen in Activity Monitor as an "Intel (64 bit)" process. When I reboot my mac and check the process by the Activity Monitor, the httpd process is flagged as "intel" - which is what I expect to see. I have also confirmed from the Arch documentation that /Library/LaunchDemons should be processed before /System/Library/LaunchDaemons To /Library/LaunchDaemons/Īnd added a flag run Apache in 32 bit mode: arch
#MAC OS X APACHE EXECUTE DRIVER#
I am in the process of trying to get a PHP PDO MySQL driver up and running under Leopard and I am basically following ideas from Tom Gidden in forcing Apache to run as i386 instead of the Leopard default of x86_64.Īs per Tom's ideas I have copied /System/Library/LaunchDaemons/