From owner-freebsd-current Wed Jul 23 17:46:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA26978 for current-outgoing; Wed, 23 Jul 1997 17:46:32 -0700 (PDT) Received: from shell.uniserve.com (tom@shell.uniserve.com [204.244.210.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26969 for ; Wed, 23 Jul 1997 17:46:29 -0700 (PDT) Received: from localhost (tom@localhost) by shell.uniserve.com (8.8.5/8.8.5) with SMTP id RAA25338; Wed, 23 Jul 1997 17:44:56 -0700 (PDT) X-Authentication-Warning: shell.uniserve.com: tom owned process doing -bs Date: Wed, 23 Jul 1997 17:44:55 -0700 (PDT) From: Tom To: Warner Losh cc: current@FreeBSD.ORG Subject: Re: lpr/lpd changes In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 23 Jul 1997, Warner Losh wrote: > In message Tom writes: > : Unrelated: why on earth is lpd started by the default rc* stuff? Seems > : unwise to fire up something that needs to be configured to be useful > : first. > > That's a good question. would it make sense to have a grep for ^lp in > /etc/printcap before starting it? Or at least for lines not being > blank and not starting with #. It might not be worth the effort. Configuring lpd can be complex, and make require additional packages (ex. ghostscript, and apsfilter) to be useful. Anyone who gets through the process should have much trouble turning the NO to YES in rc.conf (or is is ON and OFF now?). > Warner > Tom