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.

Alright, this time on time and not weeks behind the official release like the last update of Postfix. Wietse released a minor bug-fix which solves some problems in the SMTP client. The bug-fixes include:

• A remote SMTP client TLS certificate with an unparsable canonical
  name triggered a panic error in the Postfix SMTP server (attempt
  to allocate zero-length memory) while sending a request to an
  SMTPD policy server.
• On backup MX servers where the queue file system is mounted with
  “atime” (file read/execute access time) updates disabled, the
  flush daemon would trigger mail delivery attempts once every 1000
  seconds, thus rendering the maximal_backoff_time setting useless
  for backup MX service.

This update has been tested on my test server and my production server is using this latest release as well for a few hours now without a problem.

By the way as a sidenote, I’ve ordered my Leopard box in the online Apple store. I need to prepare my test server for the upgrade!

Roundcube got another new release candidate. This updated version has a lot of improvements and fixed bugs. HTML message composition is also included but by disabled by default because it’s still experimental.

I wonder how long it will be before we see a proper regular release. For more than a year it has been nothing but beta and RC’s. The product is stable enough to be used in a production environment and has enough features to be able to use it daily. I wonder what is keeping it from releasing it properly.

To update roundcube, if you’ve used the DIYMacServer provided installation instructions, and if you are upgrading from RC1 are:

Extract the RC2 archive into '/Library/WebServer/Documents'. Create new copies of the configuration files and edit them to reflect the same settings as in the RC1 installation.

Remove the original ’roundcubemail’ symbolic link and create a new one:

sudo ln -s /Library/WebServer/Documents/roundcubemail-0.1-RC2 /Library/WebServer/Documents/roundcubemail

Nothing more to do ! If you have an older version it’s necessary to recreate the database because it has changed. Just do a ‘drop databasename’ and run the sql scripts as explained in the installation documentation.

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 ?

Allright, the update for Courier-Auth that solves the bug found when using with Mac OSX is released. There where some other issues that were fixed in the IMAP server and some other small bugs in other parts of the courier software stack that we don’t use in our setup. The bug fixes that concern us are:

• courier-authlib: portability fix for the check of the highest available file descriptor, this is the one we reported on earlier
• imap: Fix crash during ‘make check’ on some platforms
• imap: Avoid a double-fclose in a marginal error condition

I’ve tested these new releases (0.60.2 for Courier-Auth and 4.2.1 for Courier-IMAP) and they work, don’t forget to do a:
sudo chmod o+x /usr/local/var/spool/authdaemon
after you’ve done a ‘make install’ on the courier-auth daemon.