Slightly more information on this.  There definitely seems to be some
sort of problem with LPRng getting printcap info from a file.

> echo bptest|pcap-query > /etc/printcap
> 
> ...  and told lpd.conf to use this.
> 
> And now everything works fine.

As a further test, I put the contents of the everything-working-OK
/etc/printcap above into a program which merely cats it to STDOUT:

[pancakes]toby: cat ~/tmp/pcap-query.test
cat <<EOF
bptest|testing:tc=.hpcommon_nohpdriver:tc=.krbserver
.hpcommon_nohpdriver|tc entry for HP printers (uses socket interface on 
printer):lp=%P.inf.ed.ac.uk%9100:sd=/var/spool/lpd/%P:sh:mx=0:mc=0:if=/usr/share/printing/psif:stalled_time#600:ac=acct
.krbserver|kerberos server-side auth data:kerberos_keytab=/etc/lpd.keytab
EOF
[pancakes]toby:

... and changed lpd.conf, so it looks here for printcap information:

[pancakes]root: grep printcap_path /etc/lpd/lpd.conf
#printcap_path=| -$ /usr/bin/pcap-query
#printcap_path=/etc/printcap
printcap_path=| -$ /home/toby/tmp/pcap-query.test

... and it's broken again, with the same error from checkpc.

Note that this is testing the exact same printcap information in
/etc/printcap (works OK) and coming from a program (doesn't work).

Should I submit this as a bug and if so, how do I do it?

Cheers
Toby


-----------------------------------------------------------------------------
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