Date: Tue, 3 Jul 2001 19:50:16 -0400 From: Garance A Drosihn <drosih@rpi.edu> To: peeter@pirns.net, freebsd-questions@FreeBSD.ORG Subject: Re: lpc start failure Message-ID: <p05101011b768088a99fc@[128.113.24.47]> In-Reply-To: <20010703001800.A776@rhubarb.pirns.net> References: <20010703001800.A776@rhubarb.pirns.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:18 AM -0500 7/3/01, Peeter Pirn wrote: >For the record: `man lpd' conflicts with reality on my >3.2-RELEASE machine. The problem is that you're running a very old snapshot of the operating system. It would be very good if you could update your machine to a newer version, even if it's just a more recent version of the release-3 branch. Release 3.2 is from about June of 1999. >On my machine, the lock file needs to be removed even after >running `lpc stop', like a good boy: > ># lpc stop lp2 >lp: > printing disabled ># lpc start lp2 >lp: > printing enabled > daemon started ># lpc status lp2 >lp: > queuing is enabled > printing is disabled > no entries in spool area > printer idle This is a bug in the 'lpc start' command, which was fixed on January 24th, 2000 (revision 1.12.2.2 of lpc/cmds.c). That's what went out with 3.5-RELEASE. (if this bug bothers you, and you don't want to update your entire operating system, you could just get that version of lpr/lpc and just compile and install that). -- 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?p05101011b768088a99fc>