Lion

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.

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.1

Having a brand new installation running with Lion for a few weeks now on my new production machine and it’s running like a dream. Just installed the OS X update to 10.7.1, rebooted and had my fingers crossed as I had not rebooted the machine yet. After the reboot did a bunch of checks and everything was running fine. Indicating that the upgrade does not have any impact on our new setup (as was the intention of moving everything into /usr/local) which is great but also indicated that my installation from scratch went find as well and I had not missed any startup- script.

So feel free to upgrade and keep me posted of any issues you might find.

Site moved to new mini at Macminicolo

This weekend I’m moving all my sites and email to a newer mini again at macminicolo, as they rock (for real). My older production mini was a core duo Intel one which was still running Leopard (could not find the courage to upgrade with no backup machine available). Getting a newer machine (a 2 year old Core 2 Duo) also meant I could upgrade to Lion. I’ve installed the new machine from scratch and I’m currently moving site for site and email per domain to make sure that everything goes seamless for the end users.

If you are reading this you are looking at the new mini running Lion!

Why not buy the latest hardware you might ask, because it cost a lot more then a second hand and I really don’t need the power of it. All the sites and mail running on my mini are not giving it a real hard time. If I got slasdotted/fireballed I’ve got WordPress tuned with caching and could handle some load. The highest I got was 10.000 page views in a day, no sweat…

Next Page »