Mac OS X

Startup script locations

I once thought that the location for the start up scripts should be in /System/Library/LaunchDaemons which I had read in other webpages I had found at the time. Never questioning what I had found as I didn’t know any better and it all worked.

Until last week a comment added to the Apache startup script page by Anonymouse started to get me thinking, where my assumptions correct. The upgrade to Mountain Lion and the disappearance of all my startup scripts from /System/Library/LaunchDaemons pushed me over. After doing some research I hound the following overview of where which scripts should be:

    ~/Library/LaunchAgents          Per-user agents provided by the user.
     /Library/LaunchAgents          Per-user agents provided by the administrator.
     /Library/LaunchDaemons         System wide daemons provided by the administrator.
     /System/Library/LaunchAgents   OS X Per-user agents.
     /System/Library/LaunchDaemons  OS X System wide daemons.

Therefore I’ve now decided to amend the documentation and put all my scripts in /Library/LaunchDaemons. I hope you all agree that this is a better place.

Mountain Lion progress

If you are dependent on any of the stuff that is documented here then please wait while I upgrade and test all the instructions for Mountain Lion. I will update this post regularly with my progress. Currently I’m upgrading my main desktop to see if this will affect the running setup. After that I will install a clean Mountain Lion machine for documenting the start from scratch.

First discovery after the upgrade is that all you config files in /etc are gone, so are our startup scripts in /System/Library/LaunchDeamons. This means that the config for Apache, php and MySQL are missing.

Got MySQL running by replacing the startup script. Apache ran again after restoring /etc/httpd from a backup but PHP needed recompiling.

Before upgrading make sure you make a copy of the file InstallESD.dmg from the Mountain Lion installer package. How to find it, read this. This because you need to get an optional installer package if you want to use GD. Mount the disk image and install the file from Packages called X11redirect.pkg

The MAMP stack is now done, tested and documented. Not many changes…

Mail part is now also documented!

ClamAV update – 0.93.4

There is a update for ClamAV available for download. The current version is 0.97.4. Upgrading is relatively easy and straight forward. All that needs to be done is remove the old version and install the new.

You can check the instructions on what to do here Upgrading ClamAV.

There is no need to reconfigure anything.

For those that are interested. This version of ClamAV has on access scanning available under OS X 10.5 and later. For more information please check the ClamAV website here -> http://www.clamav.net/lang/en/2012/03/21/on-access-scanning-for-os-x/

Mac OS X Update 10.7.3 and Security Update 2012-001

Apple released an update to Lion bringing it to version 10.7.3 and introduced a security update to Snow Leopard. If you followed the latest set of instructions where everything was located in /usr/local then these updates wouldn’t have affected you. However for all the people who are still on the original setup you will have been impacted as this security update installs and overwrites PHP and Postfix. The solution to this is still the same go into the source directory of the last installed version and run a “sudo make install” for PHP and Postfix, restart Apache and Postfix and everything is back in order again. You might also need to comment out the line:

inet_interfaces = localhost

from “/etc/postfix/main.cf

Try to migrate as soon as possible to the new setup to save you from future problems with the next security update.

The funny thing is that when you read the content of the security update details you will see that if you followed our update strategy you will use more recent stuff for your web and mail server then is included in this update. Example: After the update you will have Apache 2.2.21 while we are on 2.2.22 and the buid in PHP will be updated to 5.3.8 while we are on 5.3.10. This proves my point that you are better of doing this kind of stuff yourself without waiting for Apple or someone else to provide you with the updates.

Here you don’t even need me, I only help in the testing and eventual problem fixing if something goes wrong…

Mac OS X Update 10.7.2 and Security Update 2011-006

Sorry for this late post, but it is by many things like a short holiday and illness…

If you followed the latest set of instructions where everything was located in /usr/local then these updates wouldn’t have affected you. However for all the people who are still on the original setup you will have been impacted as this security update installs and overwrites PHP and Postfix.

The solution to this is still the same go into the source directory of the last installed version and run a “sudo make install” for PHP and Postfix, restart Apache and Postfix and everything is back in order again. You might also need to comment out the line:

inet_interfaces = localhost

from “/etc/postfix/main.cf

Try to migrate as soon as possible to the new setup to save you from future problems with the next security update.

Next Page »