Yep I had this problem too when putting qmail on a machine in a DMZ.
Naturally I didn't want ny build tools on the machine.
It was a major pain to fix all the permissions and get qmail running. In
fact it took me about 4 - 6 hours to get it all bedded down (Luckily I had
another qmail installation behind the firewall that I could use for
reference).
Someone should write a HOWTO explaining howto compile on one machine and
deploy on another.
Wilson Fletcher
On Thursday, June 03, 1999 5:40 PM, Emmanuel Mogenet
[SMTP:[EMAIL PROTECTED]] wrote:
> >Sounds like maybe your "trigger" is messed up. If you can, do a "make
> >check" from the source tree. Else, do:
> >
> > ls -l /var/local/qmail/queue/lock/trigger
> >
> >And make it look like:
> >
> >prw--w--w- 1 qmails qmail 0 Jun 3 13:25
> /var/local/qmail/queue/lock/trigger
>
> That did it.
>
> I had it prw-------
>
> >Your /var/qmail/queue/lock/trigger either isn't a pipe, or it's
> >permissions are hosed. cd /usr/local/src/qmail-1.03; make setup.
>
> One annoying problem with qmail is the following:
>
> The machine I built it on and the machine I compile it on are not the
same.
>
> The machine it runs on is a barebones firewall that doesn't have anything
such
>
> as make, cc other goodies installed.
>
> So I have to make it on a machine, make a tarball, and install it on the
> other.
> Somehow, the w bits got lost in the transfer. Maybe a tar bug on named
pipes
> ??
>
> I'll investigate further.
>
> Thanks a lot for fixing my problem
>
> - Emmanuel
