Date: Mon, 20 Apr 2009 19:30:48 -0500 From: Adam Vande More <amvandemore@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: Can you ACTUALLY print from FreeBSD? Message-ID: <49ED13B8.50106@gmail.com> In-Reply-To: <20090420223625.8847EA3DF2@maxine.cjones.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>
next in thread | previous in thread | raw e-mail | index | archive | help
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. > > <config info snipped> > > 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49ED13B8.50106>