I'd like to offer my experiences with installing Toaster on an AMD-64
server running RedHat ES-4. I have a few RedHat "fixes" and some
stuff about vpopmail and 64-bit.
A little background. I originally set up our toaster of Debian Sarge
and then we decided to migrate our toaster to a Rackspace server for
some more network reliability. The Debian box is an older x86 (550
MHz if I remember correctly) and the new Rackspace box is an AMD-64
Redhat ES-4 install.
The first thing, to make the Freshclam section go a little easier, is
to add a 'chkconfig' line to the freshclam init script. It's a simple
one so I won't bother you with a patch.
#!/bin/sh
# chkconfig: 2345 80 30
# description: Freshclam daemon to update the ClamAV virus signatures
This should allow RedHat users to skip all the symbolic link steps by
just issuing 'chkconfig --add freshclam'. This doesn't do much for
Debian installs but should be nice for Redhat and Redhat-like setups.
Since RedHat and Debian both use stunnel4, I had to modify the run
script and create a stunnel.conf file to get pop3ds to work. It looks
like stunnel4 pulls all it's config options from the config file.
Here is my run file:
--------------------------
#!/bin/sh
VPOPMAILUID=`id -u vpopmail`
VPOPMAILGID=`id -g vpopmail`
exec /usr/local/bin/tcpserver -l 0 -R -H -v \
-u"$VPOPMAILUID" -g"$VPOPMAILGID" 0 995 \
/usr/sbin/stunnel /usr/local/etc/stunnel-pop3ds.conf \
/var/qmail/bin/qmail-popup `hostname` \
/home/vpopmail/bin/vchkpw /var/qmail/bin/qmail-pop3d Maildir 2>&1
--------------------------
And here is my stunnel-pop3ds.conf file:
--------------------------
cert = /var/qmail/control/servercert.pem
client = no
foreground = no
--------------------------
Without these changes I would see entries like this in my
/var/log/qmail/pop3ds/current log:
2006-01-10 12:21:25.278994500 2006.01.10 12:21:25
LOG3[32287:182894071904]: -f: No such file or directory (2)
2006-01-10 12:21:25.279023500
2006-01-10 12:21:25.279034500 Syntax:
2006-01-10 12:21:25.279045500 stunnel [filename] | -fd [n] | -help |
-version | -sockets
2006-01-10 12:21:25.279057500 filename - use specified config
file instead of /etc/stunnel/stunnel.conf
2006-01-10 12:21:25.279069500 -fd n - read the config file
from specified file descriptor
2006-01-10 12:21:25.279081500 -help - get config file help
2006-01-10 12:21:25.279092500 -version - display version and defaults
2006-01-10 12:21:25.279103500 -sockets - display default socket options
2006-01-10 12:21:25.279345500 tcpserver: end 32287 status 256
Lastly, getting courier-authlib to compile on AMD-64. I was
constantly getting compile errors saying something like 'libvpopmail.a
... recompile with -fPIC'. I finally found this post
(http://www.mail-archive.com/vchkpw@inter7.com/msg22444.html) and
downloaded the makefile. If it's no longer available, let me know and
I'll give you mine. Unfortunately, the tarball should've contained a
file called 'compile'. It needs to be executable and should just be
this:
--------------------------
#!/bin/sh
# WARNING: This file was auto-generated. Do not edit!
exec gcc -fPIC -O2 -c ${1+"$@"}
--------------------------
Both the tarball and this 'compile' file should be extracted in to the
vpopmail directory. Then do a 'aclocal' and 'automake' and then
reconfigure and recompile. After it builds cleanly, then follow the
steps you have for building courier-authlib.
The chkconfig trick above works for adding the startup links for
courier-authlib as well as courier-imap. The chkconfig lines is
already in the startup scripts so just a 'chkconfig --add
courier-authlib' will do it.
I hope these little tips will help the next person who tries their
install on a RedHat 64-bit box.
Regards,
--
Ken Schweigert
