From owner-freebsd-questions Fri Nov 16 22:31:43 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.rpi.edu (mail.rpi.edu [128.113.22.40]) by hub.freebsd.org (Postfix) with ESMTP id D8BAB37B417 for ; Fri, 16 Nov 2001 22:31:40 -0800 (PST) Received: from [128.113.24.47] (gilead.acs.rpi.edu [128.113.24.47]) by mail.rpi.edu (8.11.3/8.11.3) with ESMTP id fAH6Vds161166; Sat, 17 Nov 2001 01:31:39 -0500 Mime-Version: 1.0 X-Sender: drosih@mail.rpi.edu Message-Id: In-Reply-To: <3BF5C752.A0545890@Radonc17.UCSF.Edu> References: <3BF5C752.A0545890@Radonc17.UCSF.Edu> Date: Sat, 17 Nov 2001 01:31:36 -0500 To: Dave Woodruff , Questions@FreeBSD.ORG From: Garance A Drosihn Subject: Re: lpc/lpd problem - insufficient information Content-Type: text/plain; charset="us-ascii" ; format="flowed" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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