From owner-freebsd-hackers Mon Feb 5 17:26:34 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from gandalf.vi.bravenet.com (gandalf.bravenet.com [139.142.105.50]) by hub.freebsd.org (Postfix) with SMTP id B2CFE37B6A9 for ; Mon, 5 Feb 2001 17:26:16 -0800 (PST) Received: (qmail 4509 invoked by uid 1000); 6 Feb 2001 01:25:47 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 6 Feb 2001 01:25:47 -0000 Date: Mon, 5 Feb 2001 17:25:47 -0800 (PST) From: Dan Phoenix To: Alfred Perlstein Cc: Jos Backus , freebsd-hackers@FreeBSD.ORG Subject: Re: qmail IO problems In-Reply-To: <20010205165023.L26076@fw.wintelcom.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I should also state ps awwlx|wc -l or whatever returned approx 90 processes. So don;t think that is an issue here. On Mon, 5 Feb 2001, Alfred Perlstein wrote: > 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 > > * 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