Here is another episode in the problems with the mod_ssl module in Apache on Leopard. But it is a positive one. Because of the latest security update 2008-2 the default Apache install on OS X Leopard is now 2.2.8. This means we can upgrade our version as well and copy the mod_ssl module from the original installation as done previously.

I’ve looked for more workarounds, but they are all a bit drastic or don’t work. The one I haven’t tried yet is upgrading libtool as I’m not sure that would help and not break any other stuff.

You only need to do this if you need mod_ssl, if you can live without it just follow the normal installation instructions.

There is a small issue with installing MySQL on Leopard. The preference pane to start/stop Mysql does not work. Don’t know why but it just doesn’t. It will start manually but you need to make a slight adjustment to one file called ‘mysql.server’ in the directory ‘/usr/local/mysql/support-files/’. On line 62 change:

user=mysql

into

user=_mysql

The following has happened in Leopard. All the users that are used for running applications have a changed username. All the daemon users start with an underscore in Leopard. This means that the user ‘mysql’ which we remember in Tiger is currenty known as ‘_mysql’. You will see this user as the owner of ‘/usr/local/mysql/data’. So somehow everything gets installed with the correct user.

The error of the Preference pane has been logged as a bug on the MySQL bug site.

If anyone can explain why the usernames have changed I would like to know!

By the way the only difference in installing MySQL on Leopard is the configure statement to compile MySQL, the rest is still the same. The new ./configure statement for PowerPC and Intel based Macs is:

./configure --prefix=/usr/local/mysql \
--localstatedir=/usr/local/mysql/data \
--libexecdir=/usr/local/mysql/bin \
--libdir=/usr/local/mysql/lib \
--with-server-suffix=-standard \
--enable-thread-safe-client \
--enable-local-infile \
--enable-shared \
--with-zlib-dir=bundled \
--with-big-tables \
--with-readline \
--with-archive-storage-engine \
--with-innodb \
--without-docs \
--without-bench

As you see the CFLAGS have gone, the new XCode tools do their auto detection a lot better I guess.

It’s decided, Leopard is going to be released on the 26th of October. As some of you might have noticed I’ve started testing the DIYMacserver setup on an earlier build version which I found on the internet. I noticed some differences in dependancies in compiling some of the programs that we need. There are differences between Tiger and Leopard, they aren’t big but they might be crucial in your situation.

I’ve decided to write seperate documentation to inidicate the differences between Tiger and Leopard. I will buy Leopard as soon as possible, which has been made possible by the donations of some of my readers. From that moment on all effort will be put into writing and upgrading the documentation on installing everything on Leopard. I plan to write some upgrading project plan as well. I will keep you posted on the progress via this blog. The order in which I will do this is the same as the order in which the documents appear on the Docs page.

Leopard Server has some new features as well which I might incorporate in some further extensions of DIYMacServer. One of them is the Calendar server of which the source code is available. I will definitely give this one a try. The wiki is simple (just choose one), but I’m wondering which one Apple is using or did they write their own ?

Alright, I’m working on all the items on my todo list which has been growing quite heavily. The new job is so much fun that I forgot to spend time on al my other fun projects… Expect qite some posts in the next few days…

But first to the business at hand, I’ve updated the server with the Security Update 2007-7 and didn’t run into any problem with all the changes we made… Read more about the update at the apple support site. But I guess most of you already have got the update running…

Well, that was not expected, another update before we hit Leopard. It was followed by a security update a day later as well. You can install them without any issues related to our server software. There is however a problem reported with popping noises coming from the speakers on Intel Mac’s after installing this update. I haven’t noticed it myself but be warned.

More about the software update or the security update

It’s time again for a security update. It fills some new holes that could be exploited. I’ve installed it on my servers and didn’t run into any issues as expected because of the affected components don’t touch our programs. Read more about the update here. If you haven’t updated yet please do it now !

It’s time for a well needed security update. It fills some needed holes that could be exploited. I’ve installed it on my servers and didn’t run into any issues as expected because of the affected components don’t touch our programs. Read more about the update here. If you haven’t updated yet please do it now !

What a surprise, is this the last hurdle for Leopard ? I’ve udated my PPC server and haven’t ran into any issues at the moment. Everything still is working as expected. I don’t think Intel based Macs should have any problem as it looks like our programs aren’t affected.

Check out all the improvements that where made in the knowledge base article describing the update.

It’s time again for a security update. This time it’s a pure security patch and not really DIYMacServer related. It fixes a security hole in iChat, Java and Finder. I’ve installed it on my servers and didn’t run into any issues as expected because of the affected components. Read more about the update here.