From owner-freebsd-questions@FreeBSD.ORG Thu Jan 1 12:27:08 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 10EAD1065670 for ; Thu, 1 Jan 2009 12:27:08 +0000 (UTC) (envelope-from stanb@panix.com) Received: from mail2.panix.com (mail2.panix.com [166.84.1.73]) by mx1.freebsd.org (Postfix) with ESMTP id C4DC58FC1A for ; Thu, 1 Jan 2009 12:27:07 +0000 (UTC) (envelope-from stanb@panix.com) Received: from mailbackend.panix.com (mailbackend.panix.com [166.84.1.89]) by mail2.panix.com (Postfix) with ESMTP id 11EBE3480B; Thu, 1 Jan 2009 07:27:07 -0500 (EST) Received: from teddy.fas.com (c-76-26-198-188.hsd1.sc.comcast.net [76.26.198.188]) by mailbackend.panix.com (Postfix) with ESMTP id EFAA0ECEB; Thu, 1 Jan 2009 07:27:06 -0500 (EST) Received: from stan by teddy.fas.com with local (Exim 3.36 #1 (Debian)) id 1LIMdm-0003PP-00; Thu, 01 Jan 2009 07:27:06 -0500 Date: Thu, 1 Jan 2009 07:27:06 -0500 From: stan To: Free BSD Questions list Message-ID: <20090101122706.GA13049@teddy.fas.com> Mail-Followup-To: Free BSD Questions list , Stewart Flood References: <20081231212520.GA28385@teddy.fas.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20081231212520.GA28385@teddy.fas.com> X-Editor: gVim X-Operating-System: Debian GNU/Linux X-Kernel-Version: 2.4.23 X-Uptime: 07:23:03 up 234 days, 13:45, 1 user, load average: 0.00, 0.00, 0.00 User-Agent: Mutt/1.5.4i Sender: Stan Brown Cc: Stewart Flood Subject: Re: inetd.conf entry for saned? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jan 2009 12:27:08 -0000 On Wed, Dec 31, 2008 at 04:25:20PM -0500, stan wrote: > I seem to be having an inrdinate amount of trouble getting a working > inetd.conf entry for saned on 7.1 > > If I run saned from the command line, I can connect and scan. But I cannot > seem to amke it work from inetd Here is what I have: > > sane-port stream tcp nowait saned /usr/local/sbin/saned saned > > Yes, I created a user for saned. although I am suprsied that the port did > not do that. When I start inetd with the -d flag, I get: > > black# inetd -d > ADD : sane-port proto=tcp accept=1 max=0 user=saned > group=(null)class=daemon builtin=0x0 server=/usr/local/sbin/saned policy="" > inetd: sane-port/tcp: ipsec initialization failed; in entrust > inetd: sane-port/tcp: ipsec initialization failed; out entrust > inetd: enabling sane-port, fd 4 > inetd: registered /usr/local/sbin/saned on 4 > > What file do I add this line to? > For the record, here is wgat I woulnd up with, and it appears to work. In /etc/inetd.conf I have: sane-port stream tcp nowait saned /usr/local/sbin/saned saned Which is what I had, but what I was missing is TCP Wrappers, which are configuered (much to my suprise) in /etc/hosts.allow, that is where this line needed to go: sane-port proto=tcp accept=1 max=0 user=saned group=(null)class=daemon builtin=0 x0 server=/usr/local/sbin/saned policy="" Having been doing this a long time, altjough never having dealt with TCP Wrappers in the past, I recall this file having a somewhat different purpose in the pat, so I thought it was just a leagcy file. -- One of the main causes of the fall of the roman empire was that, lacking zero, they had no way to indicate successful termination of their C programs.