From owner-freebsd-questions@FreeBSD.ORG Tue May 2 14:23:04 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org 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 04EEC16A400 for ; Tue, 2 May 2006 14:23:03 +0000 (UTC) (envelope-from e.schuele@computer.org) Received: from sccrmhc14.comcast.net (sccrmhc14.comcast.net [63.240.77.84]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5E74243D49 for ; Tue, 2 May 2006 14:23:02 +0000 (GMT) (envelope-from e.schuele@computer.org) Received: from [208.206.151.59] (host59.gtisd.com[208.206.151.59]) by comcast.net (sccrmhc14) with ESMTP id <20060502142256014001aa4ne>; Tue, 2 May 2006 14:22:56 +0000 Message-ID: <44576B3F.8020804@computer.org> Date: Tue, 02 May 2006 09:22:55 -0500 From: Eric Schuele User-Agent: Thunderbird 1.5.0.2 (X11/20060426) MIME-Version: 1.0 To: FreeBSD Questions Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Cupsd strangeness.... 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: Tue, 02 May 2006 14:23:04 -0000 Hello, While this should be of absolutely no real concern.... my lack of ability to resolve it is causing me sleepless nights. I'm sure this should be an easy one... I just can't seem to fix it. Everything cups related is working perfectly fine. However, my dmesg shows the following: Starting cupsd. Starting cupsd. cupsd: Child exited with status 48! Usage: cups {reload|restart|start|status|stop} And its driving me crazy! Cupsd is trying to start twice? and the second time is giving an error. What have I done wrong here? [~] % ls /etc/rc.d | grep cups [~] % ls /usr/local/etc/rc.d | grep cups cups.sh.delme* cups.sh.sample* cupsd.delme* cupsd.sample* cupsd.sh* [~] % grep cups /etc/rc.conf cupsd_enable="YES" #cups_enable="YES" Using FreeBSD 6.1-RC as of Sat some time... but had this problem quite a while. I'm sure it started the last time I rebuilt the machine (two month back maybe). And I'm sure its a config error on my part. Any help is appreciated. -- Regards, Eric