From owner-freebsd-questions  Tue Feb 27 13:35:50 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from wasp.eng.ufl.edu (wasp.eng.ufl.edu [128.227.116.1])
	by hub.freebsd.org (Postfix) with ESMTP id B8CFD37B71C
	for <questions@freebsd.org>; Tue, 27 Feb 2001 13:35:43 -0800 (PST)
	(envelope-from bob@eng.ufl.edu)
Received: from eng.ufl.edu (scanner.engnet.ufl.edu [128.227.152.221])
	by wasp.eng.ufl.edu (8.9.3/8.9.3) with ESMTP id QAA13812;
	Tue, 27 Feb 2001 16:35:40 -0500 (EST)
Message-ID: <3A9C1DAC.BEBF35AF@eng.ufl.edu>
Date: Tue, 27 Feb 2001 16:35:40 -0500
From: Bob Johnson <bob@eng.ufl.edu>
X-Mailer: Mozilla 4.76 [en] (X11; U; Linux 2.2.12 i386)
X-Accept-Language: en, eo
MIME-Version: 1.0
To: tcpo@yahoo.com
Cc: questions@freebsd.org
Subject: Re: problem about remote printing
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Date: Mon, 26 Feb 2001 23:17:23 -0800 (PST)
> From: Tak-Chi PO <tcpo@yahoo.com>
> Subject: problem about remote printing
> 
> I have a HP4050 at 192.168.1.54.  Here is my
> /etc/printcap:
> 
> remote|lp:\
>         :sh:\
>         :rm=192.168.1.54:\
>         :sd=/var/spool/output/lp54:\
>         :lf=/var/log/lpd-errs
> 

It probably has nothing at all to do with your problem, but you 
might want to add an "rp=..." line (e.g. rp=text) to this to 
tell the printer what mode to use.  Or it may be completely 
unnecessary for your printer.

You will probably want add "mx#0" as well, because the default 
maximum file size of 1 megabyte is likely to be too small for 
large print jobs.  mx#0 makes that unlimited (actually, limited 
by the available space in /var/spool).


> after i tried to print sth, i run "lpc status all", I
> se:
> 
> remote:
>       queuing is enabled
>       printing is enabled
>       4 entries in spool area
>       waiting for 192.168.1.54 to come up
> 
> It is "waiting to come up" forever and nothing's get
> printed.  What's possibly wrong here?

What does "ps ax | grep lpd" tell you?

When I've had similar problems, it was usually because I 
didn't have lpd running on my local system.  lpd must be 
running on your local system in order to send print jobs 
to remote systems.  I don't remember what you would see 
for lpc status if that was the problem, though.  I find 
lpc to be an unreliable method of diagnosing or fixing 
printer problems, but maybe that's because I don't really 
understand it.

If that is the problem, you can enable lpd to start 
automatically in rc.conf.

- Bob

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message