From owner-freebsd-questions@FreeBSD.ORG Sat Jun 21 20:52:13 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1A3C237B401 for ; Sat, 21 Jun 2003 20:52:13 -0700 (PDT) Received: from beck.quonix.net (beck.quonix.net [64.239.136.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9FB7843F93 for ; Sat, 21 Jun 2003 20:52:12 -0700 (PDT) (envelope-from john@essenz.com) Received: from essenz.com (pcp04098733pcs.neave01.pa.comcast.net [68.80.102.17]) by beck.quonix.net (8.12.9/8.12.9) with ESMTP id h5M3q3E7062801; Sat, 21 Jun 2003 20:52:03 -0700 (PDT) (envelope-from john@essenz.com) Date: Sat, 21 Jun 2003 23:50:21 -0400 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) From: John Von Essen To: matusita@jp.FreeBSD.org, freebsd-questions@freebsd.org Content-Transfer-Encoding: 7bit In-Reply-To: <20030622115331F.matusita@jp.FreeBSD.org> Message-Id: X-Mailer: Apple Mail (2.552) Subject: Re: rc.sendmail X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Jun 2003 03:52:13 -0000 Okay, before people send more responses... Yes, I have looked at man rc.sendmail and I do understand how everything works. My question is WHY was it designed to behave they way it does? Why isn't rc.sendmail setup such that you can start the listening daemon for inbound, queue runner for outbound, and the msp queue runner. (Currently, you cant start that config with rc.conf and rc.sendmail due to rc.sendmail's logic) Obviously, you can't run the localhost submission daemon AND the port 25 remote daemon listening for inbound. For that case, it is either one or the other - so that part of rc.sendmail makes sense. But if I select "YES" to enable both the mqueue runner and the clientmqueue runner in rc.conf, the rc.sendmail script will not perform this. The logic of rc.sendmail will only start mqueue if sendmail and sendmail submit are set to "NO". Likewise, if you select sendmail "YES", then the only other thing you can run is the clientmqueue runner. In my case, I need to run the sendmail daemon, the mqueue runner, and the clientmqueue runner. In other words, I need the following at startup: /usr/sbin/sendmail -L sm-mta -bd -q1h /usr/sbin/sendmail -L sm-mqueue -qp5m /usr/sbin/sendmail -L sm-clientmqueue -Ac -qp5m rc.conf and rc.sendmail cannot startup what I want. As a result, I have to do sendmail_enable="NONE", and then from rc.local startup what I want manually. Why can't rc.sendmail be designed such that whatever has "YES" in rc.conf will get started? John On Saturday, June 21, 2003, at 10:53 PM, Makoto Matsushita wrote: > > john> Could someone please explain rc.sendmail to me? > > Is rc.sendmail(8) not enough for you? > > -- - > Makoto `MAR' Matsushita > >