On Tue, Mar 28, 2000 at 05:27:01PM +0300, Mitja Sarp wrote:
> On Mon, Mar 27, 2000 at 11:21:10AM -0600, blair christensen wrote:
> > Hello,
> > I am running Qmail 1.03 with the LDAP patch from http://www.nrg4u.com
> > on a Solaris 2.6 box. LDAP is OpenLDAP 1.2.9 residing on the same
> > box.
> >
> > The patch applies cleanly to the source, and I'm able to compile qmail
> > successfully. However, when I try to start qmail, I get:
> >
> > bash-2.02# /var/qmail/rc
> > alert: cannot start: hath the daemon spawn no fire?
> >
> > bash-2.02# cat /var/qmail/rc
> > #!/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 "`cat /var/qmail/control/defaultdelivery`"
> >
>
> I had exactly the same problem on some hosts, daemon not starting
> even with all ldap files in place. The problem was the 'exec env -'
> construction that probably failed since I was able to start everything
> with qmail-start from my shell (zsh) without problems, having /var/qmail/bin
> exported in PATH. So the fix was:
>
> % cat /var/qmail/rc
> #!/usr/bin/zsh
>
> export PATH=/var/qmail/bin:$PATH
> qmail-start ./Maildir/
>
hrm, well, tried that. same results. i then tried to run qmail-start
directly from my shell. same results.
bash-2.02# export PATH=$PATH:/var/qmail/bin
bash-2.02# which qmail-start
/var/qmail/bin/qmail-start
bash-2.02# qmail-start ./Maildir
alert: cannot start: hath the daemon spawn no fire?
perplexed,
blair
