Software-update: MySQL 3.23.54c

Kort na het verschijnen van MySQL 3.23.54 zijn er versie 54a en 54b verschenen, deze bevatten echter allemaal een select aantal bugs/compileer fouten waardoor nu dan toch MySQL 3.23.54c is uitgebracht. De volgende woorden wisseling komt met deze release:

> Ok, here you go:
> # ldd /usr/local/mysql-max-3.23.54a-pc-linux-i686/bin/mysqld
> libdl.so.2 => /lib/libdl.so.2 (0x40020000)
> libpthread.so.0 => /lib/libpthread.so.0 (0x40024000)
> libz.so.1 => /usr/lib/libz.so.1 (0x4003a000)
> libcrypt.so.1 => /lib/libcrypt.so.1 (0x40049000)
> libnsl.so.1 => /lib/libnsl.so.1 (0x40077000)
> libm.so.6 => /lib/libm.so.6 (0x4008c000)
> libc.so.6 => /lib/libc.so.6 (0x400ae000)
> libnss_files.so.2 => /lib/libnss_files.so.2 (0x401c1000)
> libnss_dns.so.2 => /lib/libnss_dns.so.2 (0x401cb000)
> libresolv.so.2 => /lib/libresolv.so.2 (0x401cf000)
> /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0x40000000)
>
> While:
> # ldd /usr/local/mysql-max-3.23.53a-pc-linux-gnu-i686/bin/mysqld
> not a dynamic executable
> (doh, that one worked )

OK, as I already assumed, the Max binary was not linked statically. Doh!
Interesting, that this also causes the load to spike, even though it's not statically linked against an unpatched glibc.

> > What version of Linux are you using?
> Running Slackware 8.1 GNU/Linux, kernel 2.4.17, GNU libc 2.2.3
>
> Have fun recompiling

Thanks. Could you please give this one a try? If this one solves the problem, I will publish it on our download pages ASAP.

Sorry about that - it seems like getting out that security update as fast as possible caused too many glitches here...

Bye,
LenZ