I just tried to upgrade to 3.7.1, and have discovered a problem with
:tc= entries.  They don't work.  Specifically, my printcap contains:
_lpr
        :sd=/var/spool/lpd/%P
        :lf=/var/log/lpd-errs
        :of=/usr/libexec/filters/ofhp
        :if=/usr/libexec/filters/ifhp
        :vf=/usr/libexec/filters/ifhp -c
a001|A001:[EMAIL PROTECTED]:ifhp=model=hp3si:tc=_lpr
[chomp]

checkpc tells me:
2000-12-13-10:31:58.773 tandem a001: Fixup_pc_info: tc entry '_lpr'
not found

When I run 'checkpc -D4', I see what looks like two calls to
Find_str_value.  One with "key '_lpr', value '_lpr'", and one with
"key '_lpr', value '<NULL>'".  After the second call, Fixup_pc_info
complains, and everything exits.  If anything, it looks like the
variable 'name' is getting set to NULL (which seems to be the wrong
thing). 


-- 
=====================================================================
| JAVA must have been developed in the wilds of West Virginia.      |
| After all, why else would it support only single inheritance??    |
=====================================================================
| Finger [EMAIL PROTECTED] for my public key.                            |
=====================================================================


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