From mboxrd@z Thu Jan  1 00:00:00 1970
From: Roger Leigh <roger.leigh@epictechnology.co.uk>
Subject: Re: unable to print to lpt1
Date: Wed, 21 Sep 2005 16:40:58 +0100
Message-ID: <20050921154058.GA17648@epictechnology.co.uk>
References: <1127293783.10462.6.camel@husain.site>
Mime-Version: 1.0
Return-path: <linux-msdos-owner@vger.kernel.org>
Content-Disposition: inline
In-Reply-To: <1127293783.10462.6.camel@husain.site>
Sender: linux-msdos-owner@vger.kernel.org
List-Id: <linux-msdos.vger.kernel.org>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: husain <husain@mweb.co.za>
Cc: linux-msdos@vger.kernel.org

On Wed, Sep 21, 2005 at 11:09:43AM +0200, husain wrote:
> lpr: error - unable to print file: client-error-not-found

This is a CUPS lpr error.  The specified print queue does not exist.

$_printer = "myqueue"
$_printer_command = "lpr"
$_printer_timeout = (5)

should be sufficient to print to LPT1, assuming the existence of a print
queue named "myqueue" on the host Linux system.  You didn't set this in
your configuration.

I sometimes use the equivalent

printer { options "-P myqueue" command $_printer_command timeout (5) }

but this is only needed when different timeouts are required for
different LPT ports.


Regards,
Roger