Hello,

First of all, please forgive me if this has been covered
already, but I was unable to find anything about it in
the mailing list archives.

Also, I am typing all of these error messages in by hand, 
since the problem computers are on an isolated network.
Typos are most likely my fault.


I am trying to get LPRng 3.7.2 working under Solaris 8 
(10/00, 64-bit mode).  My specific problem is that 
whenever I try to print something, without explicitly 
telling lp where the printer is, I get the following
message/error.  $PRINTER is set to "ps".

   jargon:cdschr1.1 > lp /etc/hosts
   Status Information:
    sending job 'cdschr1@jargon+851' to ps@localhost
    connecting to 'localhost', attempt 1
    cannot open connection to localhost - Connection refused
   Make sure LPD server is running on the server
 
My printcap file only lists client information and I 
compiled LPRng with the force_localhost option turned off.

The printcap file I am currently using looks like this:

   0|lw|ps|postscript|Postscript|PostScript:
      :lp=pea3anaheim@print-spool-0:
      :client:

In the course of my testing, I have also added the 
":force_localhost@" directive and added "rp" and "rh" 
lines to that printcap file.  All changes still give me 
the same error message above.

When I use the -D 1 option to lp, I get the relevent 
messages included below.

The only way I am able to print from LPRng 3.7.2 is by
doing something like this:
   lp -dpea3anaheim@print-spool-0 <file>

"print-spool-0" is a DEC alpha (4.0D) running lpd from 
LPRng-3.6.x.

Is there a problem with my printcap, with something I'm 
doing, or with LPRng itself?


Thank you for your help,
chad



Relevant output from lp -D 1 /etc/hosts:
[I've removed the timestamps, as that is a lot to type.]

jargon [24851] lp Build_printcap_info: list->count 0, raw->count 3
jargon [24851] lp Build_printcap_info: list->count 0, raw->count 0
jargon [24851] lp Get_parms: LP_mode 1
jargon [24851] lp Get_parms: option D
jargon [24851] lp Get_printer: original printer '<NULL>'
jargon [24851] lp ps: Get_printer: final printer 'ps'
jargon [24851] lp ps: Fix_Rm_Rp_info: printer name 'ps'
jargon [24851] lp Reset_config: starting
jargon [24851] lp ps: Select_pc_info: looking for 'ps', depth 0
jargon [24851] lp ps: Select_pc_info: names[0] 'lp=lp'
jargon [24851] lp ps: Select_pc_info: trying 'lp'
jargon [24851] lp ps: Select_pc_info: returning '<NULL>'
jargon [24851] lp ps: Select_pc_info: looking for '*', depth 0
jargon [24851] lp ps: Select_pc_info: names[0] 'lp=lp'
jargon [24851] lp ps: Select_pc_info: trying 'lp'
jargon [24851] lp ps: Select_pc_info: returning '<NULL>'
jargon [24851] lp ps: Select_pc_info: looking for 'ps', depth 0
jargon [24851] lp ps: Select_pc_info: names [0] 'lp=lp'
jargon [24851] lp ps: Select_pc_info: trying 'lp'
jargon [24851] lp ps: Select_pc_info: returning '<NULL>'
jargon [24851] lp ps: Select_pc_info: looking for '*', depth 0
jargon [24851] lp ps: Select_pc_info: names[0] 'lp=lp'
jargon [24851] lp ps: Select_pc_info: trying: 'lp'
jargon [24851] lp ps: Select_pc_info: returning '<NULL>'
jargon [24851] lp ps: Fix_Rm_Rp_info: Printer 'ps', Queue 'ps', \
    Lp '<NULL>', Rp 'ps', Rh 'localhost'
jargon [24851] lp ps: lpr: Lpr_opts_DYN '<NULL>', argc 4
jargon [24851] lp ps: Make_job: before checking format ''

-------


--
chad at radix dot net

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