From: Roger Leigh <roger.leigh@epictechnology.co.uk>
To: husain <husain@mweb.co.za>
Cc: linux-msdos@vger.kernel.org
Subject: Re: unable to print to lpt1
Date: Wed, 21 Sep 2005 16:40:58 +0100 [thread overview]
Message-ID: <20050921154058.GA17648@epictechnology.co.uk> (raw)
In-Reply-To: <1127293783.10462.6.camel@husain.site>
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
next prev parent reply other threads:[~2005-09-21 15:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 9:09 unable to print to lpt1 husain
2005-09-21 15:40 ` Roger Leigh [this message]
[not found] ` <200509241221.21332.husain@mweb.co.za>
2005-09-26 15:31 ` Roger Leigh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20050921154058.GA17648@epictechnology.co.uk \
--to=roger.leigh@epictechnology.co.uk \
--cc=husain@mweb.co.za \
--cc=linux-msdos@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.