From owner-freebsd-questions@FreeBSD.ORG Tue Apr 21 00:31:18 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 E14031065680 for ; Tue, 21 Apr 2009 00:31:18 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from imedmobility.com (host-50.216-16-29.iw.net [216.16.29.50]) by mx1.freebsd.org (Postfix) with ESMTP id 965C58FC1D for ; Tue, 21 Apr 2009 00:31:18 +0000 (UTC) (envelope-from amvandemore@gmail.com) Received: from midco.net (host-67-54-107-208.midco.net [208.107.54.67]) by imedmobility.com (Postfix) with ESMTPA id 10C831173C5C for ; Mon, 20 Apr 2009 19:31:16 -0500 (CDT) Message-ID: <49ED13B8.50106@gmail.com> Date: Mon, 20 Apr 2009 19:30:48 -0500 From: Adam Vande More User-Agent: Thunderbird 2.0.0.21 (X11/20090408) MIME-Version: 1.0 To: freebsd-questions@freebsd.org References: <20090420145839.5D396A3DC7@maxine.cjones.org> <86fxg3gwny.fsf@nowhere.org> <20090420173603.8CF7EA3DC7@maxine.cjones.org> <9B2BDFC5F4D9083916FFE187@utd65257.utdallas.edu> <20090420192048.40290A3D2E@maxine.cjones.org> <62CFD48735EA944E20668C98@utd65257.utdallas.edu> <20090420223625.8847EA3DF2@maxine.cjones.org> In-Reply-To: <20090420223625.8847EA3DF2@maxine.cjones.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Can you ACTUALLY print from FreeBSD? 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, 21 Apr 2009 00:31:19 -0000 Keith Seyffarth wrote: >> Googling that shows it to be a file shared with Windows boxes when you're >> running samba. I don't know if you set up samba or not, but I would ignore >> this error for now. It's likely unrelated to the printing problem that you're >> having. >> > > OK. Thanks. I guess. I was kind of hoping that figuring that out might > be the fix... > > >>>> Do you have the startup script: >>>> /usr/local/etc/rc.d/cupsd ? >>>> >>> yes >>> >>> >>>> If so, what is the output of /usr/local/etc/rc.d/cupsd status? >>>> >>> currently it's: >>> cupsd is running as pid 721. >>> >>> but I did start cups manually since my last reboot. >>> >>> >> Cupsd was started automatically on reboot by the script. So that part is >> working fine. >> > > after rebooting the machine, it's: > cupsd is not running. > > > > This seems to me to be area to focus on. Have you tried starting if from cli and seeing if any errors show. Also check logs etc recompile cups w/ debugging info if applicable. I suspect it's not so you may have to increase the verbosity in a config file somewhere. It's been awhile since I printed from FreeBSD, but my last experience was positive and not nearly as much issue as you're having. Anyways I suspect following cupsd not starting to it's end will result in either solving the issue or at least getting to a point where it's easy to resolve. You can also try to trace back /usr/local/etc/rc.d/cupsd to see where it's failing.