From owner-freebsd-ports Thu Oct 25 9:22: 2 2001 Delivered-To: freebsd-ports@freebsd.org Received: from femail19.sdc1.sfba.home.com (femail19.sdc1.sfba.home.com [24.0.95.128]) by hub.freebsd.org (Postfix) with ESMTP id 24AE637B401 for ; Thu, 25 Oct 2001 09:21:58 -0700 (PDT) Received: from u.washington.edu ([24.176.79.249]) by femail19.sdc1.sfba.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20011025162157.BVWI15917.femail19.sdc1.sfba.home.com@u.washington.edu>; Thu, 25 Oct 2001 09:21:57 -0700 Message-ID: <3BD83C25.1010006@u.washington.edu> Date: Thu, 25 Oct 2001 09:21:57 -0700 From: paul beard User-Agent: Mozilla/5.0 (Macintosh; U; PPC; en-US; rv:0.9.5) Gecko/20011011 X-Accept-Language: en-us MIME-Version: 1.0 To: Joe Clarke Cc: jah4007@cs.rit.edu, ports@FreeBSD.ORG Subject: Re: FreeBSD Port: cups-1.1.10.1 References: <20011024144631.M34444-100000@shumai.marcuscom.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I never figured out why inetd was failing to permit connections, but since I was pressed for time, I hooked up the printer to a linux laptop, iterated thru 3 kernel builds before I could successfully enable the parallel port, and got it working with xinetd. symptomatically, cups was always running but port 515 was not open: I suspected some malformed security config on my part, since inetd had been working before I switched to xinetd. well, as it turned out, it was xinetd blocking things: in the printer stanza in xinetd.conf, the user was set to lp and he didn't exist. I changed it to daemon and hey presto . . . . it worked. xinetd -d is a Good Thing but rather verbose. Thanks for getting back to me: if anyone involved in the maintenance of xinetd is on this list, perhaps a feature to spit out bad config data like that without debug would be a useful (I didn't see anything logged in messages, buit if it gets logged, please set me straight). As it was I got several screens of output and the error message I needed came out almost immediately. Thanks again. I'm reminded once more I should have started working with FreeBSD long ago . . . . . Joe Clarke wrote: > > On Tue, 23 Oct 2001, paul beard wrote: > > >> I am having some problems getting CUPS's listener to, um, listen. It >>was working but for some perverse reason, I decided to xinetd to replace >>inetd. I have since removed xinetd, restored inetd to its rightful >>place, rebooted, still no luck. Multiple rebuilds/reinstalls of CUPS, >>which is unusual. What boneheaded thing am I missing? >> > > Well, I've never run cupsd out of inetd, but perhaps your inetd.conf file > isn't correctly setup to find cupsd. You might also want to check > /usr/local/etc/cups/cupsd.conf to make sure it is correct. Try commenting > cupsd out of inetd.conf, and see if you can start cupsd from the command > line. > > Joe To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message