From owner-freebsd-hackers Mon Feb 5 16:50:45 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from fw.wintelcom.net (ns1.wintelcom.net [209.1.153.20]) by hub.freebsd.org (Postfix) with ESMTP id F319237B491 for ; Mon, 5 Feb 2001 16:50:25 -0800 (PST) Received: (from bright@localhost) by fw.wintelcom.net (8.10.0/8.10.0) id f160oNU18155; Mon, 5 Feb 2001 16:50:23 -0800 (PST) Date: Mon, 5 Feb 2001 16:50:23 -0800 From: Alfred Perlstein To: Jos Backus Cc: Dan Phoenix , freebsd-hackers@FreeBSD.ORG Subject: Re: qmail IO problems Message-ID: <20010205165023.L26076@fw.wintelcom.net> References: <20010205135501.H26076@fw.wintelcom.net> <20010205162938.A50388@lizzy.bugworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <20010205162938.A50388@lizzy.bugworks.com>; from josb@cncdsl.com on Mon, Feb 05, 2001 at 04:29:38PM -0800 Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG * Jos Backus [010205 16:30] wrote: > On Mon, Feb 05, 2001 at 02:11:38PM -0800, Dan Phoenix wrote: > > their mail message is taken and piped to...sendmail -t > > which is a symbolic link to /var/qmail/bin/sendmail -t > > You can save an exec by piping directly into qmail-inject, which should have > the same effect (qmail's sendmail execv's qmail-inject; it sounds like you > don't need the compatibility interface). You could also do some tricky stuff if qmail has a constant reading scheme by using some sort of FIFO and a file that you fcntl lock over. You could have a simple perl script listening on the other end of the perl script and dole out email to several persistant processes. -- -Alfred Perlstein - [bright@wintelcom.net|alfred@freebsd.org] "I have the heart of a child; I keep it in a jar on my desk." To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message