I'm trying to set up a redundant "store-and-forward" mail server. This box will reside much farther towards our network periphery than the present Exchange server we are currently using. If we lose a critical internal network node for, say, a day or two, the intent is that this box will act as a "cache" until connectivity is restored, then will forward the email it has been storing to the again-available Exchange server. Natch, I am a *complete* qmail newbie. I have been over the Linux- centric qmail HOWTO at http://www.flounder.net/qmail/qmail-howto.html, and the "Life with Qmail" page at http://web.infoave.net/~dsill/lwq.html I installed the copies of daemontools and qmail bundled with OpenBSD 2.7, since this seemd the safest and quickest way. I am trying to put together a system to start qmail, based on the instructions on Dave Sill's site. I placed the initialization script he supplied in /var/qmail/etc/qmail.rc, since OpenBSD does not have the Solaris/Linux style of statup scripts (scripts in /etc/init.d, hard links/symlinks to them in /etc/rc?.d/). This is symlinked to by /usr/local/bin/qmail After installing daemontools as per Dave Sill's page, I appended the following lines to /etc/rc.local: # Daemontools stuff csh -cf 'svscan /service &' # Qmail startup if [ -f /var/qmail/etc/qmail.rc ] then /var/qmail/etc/qmail.rc fi The contents of /var/qmail/etc/rc (modified path; Dave Sill's is /var/qmail/rc) are as follows: #!/bin/sh # Using stdout for logging # Using control/defaultdelivery from qmail-local to deliver messages by default exec env - PATH="/var/qmail/bin:$PATH" \ qmail-start /var/qmail/supervise/qmail-send/log/run, /var/qmail/supervise/qmail-send/run, /var/qmail/supervise/qmail-smtpd/run, and /var/qmail/supervise/qmail-smtpd/log/run are exactly as Sill's site specifies, allowing for the changed path to /var/qmail/etc/rc. When (as root), I try to start qmail with /var/qmail/etc/qmail.rc start this is the output I see: Starting qmail: svscan. # supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error supervise: fatal: unable to start log/run: exec format error The only cure is a reboot! Can someone advise me as to what I am doing wrong? Thanks, Charles
