> From [EMAIL PROTECTED] Fri Mar 12 15:08:27 2004
> From: "Dwayne Pence" <[EMAIL PROTECTED]>
> To: "'Patrick Powell'" <[EMAIL PROTECTED]>
> Cc: <[EMAIL PROTECTED]>
> Subject: LPRng: RE: server printcap flag
> Date: Fri, 12 Mar 2004 16:11:22 -0600
>
> I have lp:remote_support=R set, and this does prevent the lpq queries to
> the terminal server, but how can I get it to look at the local queue on
> the Linux box when I do the lpq after it sees that the remote doesn't
> support the lpq, ie /var/spool/lpd/printer_name, which is where the jobs
> will actually be queued at anyway since forced-local is on ?  


You need to allow clients to get all the informaiton, but the server
only to use 'lpr':

lp:client:[EMAIL PROTECTED]:force_localhost@

lp:.....   (i.e. - the existing/standard printcap entry)
  :server:remote_support=R

>
> Thanks,
>
> Dwayne
>
> -----Original Message-----
> From: Patrick Powell [mailto:[EMAIL PROTECTED] 
> Sent: Friday, March 12, 2004 11:37 AM
> To: Dwayne Pence
> Cc: [EMAIL PROTECTED]
> Subject: Re: server printcap flag
>
> On Wed, Mar 10, 2004 at 11:55:30AM -0600, Dwayne Pence wrote:
> > Hi Patrick,
> >  
> > I am running running Redhat Linux 8, with LPRng and have a question.
> > All of the printers are hung off a terminal server with serial ports,
> > and it has a built in lpd.  So all of the printers in the printcap
> file
> > have a :rm and :rp entries.  My problem is the terminal server lpd
> > does/will not respond to lpq, lpstat requests, therefore I want the
> > queues, stats to come from the Redhat box, not the terminal server.  I
> > read an very old email from the LPRng list where you had mentioned a
> > "server" printcap flag that only lpd would read, which I thought would
> > work, but I don't think I understand how to put it in printcap.local.
> > When I added it to an already defined printer that is in printcap and
> > restarted lpd, it griped about overlapping entries, rp and lp.  Any
> > suggestions ?  
> >  
> > Thanks,
> >  
> > Dwayne Pence
>
> You want to use the 'remote_support' option to prevent the
> lpq, etc. queries.  The option has the format:
>
>     remote_support=RMQVC
> Where R= lpr, M = lprm, Q = lpq, V =lpc -v , C = lpc
>
> If you only want to use LPR then you can set:
>
> lp:remote_support=R
>
> -- 
> Patrick Powell                 Astart Technologies
> [EMAIL PROTECTED]            6741 Convoy Court
> Network and System             San Diego, CA 92111
>   Consulting                   858-874-6543 FAX 858-751-2435
> LPRng - Print Spooler (http://www.lprng.com)
>
>
> -----------------------------------------------------------------------------
> 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