Date: Sat, 17 Nov 2001 01:31:36 -0500 From: Garance A Drosihn <drosih@rpi.edu> To: Dave Woodruff <Woodruff@RadOnc17.UCSF.Edu>, Questions@FreeBSD.ORG Subject: Re: lpc/lpd problem - insufficient information Message-ID: <p05101001b81bb2ad2354@[128.113.24.47]> In-Reply-To: <3BF5C752.A0545890@Radonc17.UCSF.Edu> References: <3BF5C752.A0545890@Radonc17.UCSF.Edu>
next in thread | previous in thread | raw e-mail | index | archive | help
At 6:11 PM -0800 11/16/01, Dave Woodruff wrote:
>Dear M. Question:
> Running versions 3.4 & 4.2, when a printer gets out of sync
>with the daemon, it is nearly impossible to get the daemon to
>restart with files in place in the (dedicated) spooling directory.
>With lpr, I get:
>
>lpr -Plzrhp5 dfA000RO-LT-FBsd00.UCSFMedicalCenter.Org
>lpr: connect: No such file or directory
>jobs queued, but cannot start daemon.
>
>with lpc:
>
>lpc> start lzrhp5
>lzrhp5:
>lpc: connect: No such file or directory
> couldn't start daemon
>
>but neither one will tell me what file or directory is missing!
You are not the first person to be confused by that message.
Obviously I need to do something about that to make it much
more obvious what these commands are complaining about.
I expect that the main lpd process is not running. Either it
has died, or you did not change your /etc/rc.conf to start up
lpd, and thus the program is never started when you reboot.
As a quick test, try to do the following while logged into
root:
/usr/sbin/lpd
Wait a few seconds, and then try to do the 'lpc' command. If
that works, then you have to figure out why lpd isn't running
when you think it should be running.
You included your /etc/printcap entry, and that looked a little
odd to me. I am not sure if it really *is* odd, or if that was
just some kind of copy&paste error when you were doing the
message. If the above command does *not* work, then you might
want to look in /var/log/messages to see if there were any
error messages when lpd started up.
Another thing you might want to try is to run:
/usr/sbin/chkprintcap
and see if it prints out any warning or error messages. If it
prints out an error, then there is something about your printcap
file which will prevent lpd from ever starting up.
--
Garance Alistair Drosehn = gad@eclipse.acs.rpi.edu
Senior Systems Programmer or gad@freebsd.org
Rensselaer Polytechnic Institute or drosih@rpi.edu
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?p05101001b81bb2ad2354>