I seem to recall somewhere that the rm and rp nomenclature was being
deprecated in favor of lp=raw@taurus, or some similar nomenclature. I am very
vague on this point.
But, just guessing here, what if you put
:force_localhost@
into your printcap entry? This is supposed to turnoff force_localhost and make LPRng
clients, like lpq, consult the remote as opposed to the local host. Might be
interesting. I can't test this myself since I am not using your version of
LPRng.
Joel

On Thu, Jan 31, 2002 at 09:34:19AM +1100, Craig Small wrote:
> 
> A very wierd bug has cropped up from 3.8.2 to 3.8.4, my thanks to
> Guy T. Rice <[EMAIL PROTECTED]> for pointing this out to
> me.
> 
> Take a printcap like this:
> 
> lp|lj2100|HP LaserJet 2100TN:\
>         :sd=/var/spool/lpd/lj2100:rp=raw:rm=taurus:\
>         :sh:pw#80:pl#66:px#1440:mx#0:\
>         :if=/etc/magicfilter/psonly1200-filter:\
>         :af=/var/log/lp-acct:lf=/var/log/lp-errs:
> 
> lpq says this:
> 
> Printer: lp is raw@localhost
> Printer: raw@wufei - ERROR: spool queue for 'raw' does not exist on server wufe
>    non-existent printer or you need to run 'checkpc -f'
> 
> lp is not raw@localhost, lp is raw@taurus !
> 
> But changing the printcap to below fixes it:
> lp|raw|lj2100|HP LaserJet 2100TN:\
>         :sd=/var/spool/lpd/lj2100:rp=raw:rm=taurus:\
>         :sh:pw#80:pl#66:px#1440:mx#0:\
>         :if=/etc/magicfilter/psonly1200-filter:\
>         :af=/var/log/lp-acct:lf=/var/log/lp-errs:
> 
> See the raw is now included in the printcap entry?
> 
> I get lots and lots of reports about these problems.  I don't know if it
> is a lprng bug or a problem with the printcap.  I'd love to have a
> canned answer to people who have this configuration in their printcap.
> Remember, the first printcap worked with 3.8.2
> 
>   - Craig
> 
> -- 
> Craig Small VK2XLZ  GnuPG:1C1B D893 1418 2AF4 45EE  95CB C76C E5AC 12CA DFA5
> Eye-Net Consulting http://www.eye-net.com.au/        <[EMAIL PROTECTED]>
> MIEEE <[EMAIL PROTECTED]>                 Debian developer <[EMAIL PROTECTED]>
> 
> -----------------------------------------------------------------------------
> YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
> The address you post from MUST be your subscription address
> 
> If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
> or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
> to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
> with:                           | example:
> subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
> unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]
> 
> If you have major problems,  send email to [EMAIL PROTECTED] with the word
> LPRNGLIST in the SUBJECT line.
> -----------------------------------------------------------------------------

-----------------------------------------------------------------------------
YOU MUST BE A LIST MEMBER IN ORDER TO POST TO THE LPRNG MAILING LIST
The address you post from MUST be your subscription address

If you need help, send email to [EMAIL PROTECTED] (or lprng-requests
or lprng-digest-requests) with the word 'help' in the body.  For the impatient,
to subscribe to a list with name LIST,  send mail to [EMAIL PROTECTED]
with:                           | example:
subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
unsubscribe LIST <mailaddr>     |  unsubscribe lprng [EMAIL PROTECTED]

If you have major problems,  send email to [EMAIL PROTECTED] with the word
LPRNGLIST in the SUBJECT line.
-----------------------------------------------------------------------------

Reply via email to