> From [EMAIL PROTECTED] Wed Apr 24 00:31:34 2002
> Date: Wed, 24 Apr 2002 08:47:45 +0200 (CEST)
> From: Villy Kruse <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: Re: LPRng: Re: lpq changin timeouts on "cannot open connection"
>
> On Tue, 23 Apr 2002, Ryan Novosielski wrote:
>
> > Date: Tue, 23 Apr 2002 17:55:05 -0400 (EDT)
> > From: Ryan Novosielski <[EMAIL PROTECTED]>
> > Reply-To: [EMAIL PROTECTED]
> > To: [EMAIL PROTECTED]
> > Subject: Re: LPRng: Re: lpq changin timeouts on "cannot open connection"
> > 
> > It's been awhile since I tried to fix this, but I noticed the same
> > problem, and I would like to be able to do the same thing Villy wants to
> > do...
> > 
>
>
> Not "wants to do".  When you split the mailcap entry in a :server and
> a :client part, there is no problem, as lpq will use the specs with
> the :client flag and lpd will use the specs with the :server flag.
>
> Then you add :remote_support=R to the part with the :server.
>
> After all: the :server and :client flags is there to allow you to specify
> different rules for lpq and lpd.
>
> Don't know if anyone could think of a more elegang solution, or if is even
> wortwhile to change things as it is.
>
> Villy

Hmmm... mutter mutter... OK OK I just KNOW that some of you will not
like this idea...

Printcap '' information:

any key starting with 'server_xxx' will be used to set the xxx value
on the server.  This allows you to do:

lp:
  :server_remote_support=R         -> remote_support=R for LPD 
  :[EMAIL PROTECTED]       -> lp=lp@localhost for LPD
  :server_filter=...               -> filter=...      for LPD

Sigh... its ugly,  but it DOES allow you to have a single printcap entry
with both LPD server and client information.

And I already have the code in LPRng to do this...

In the initialization code add the following:
        if( Is_server ){
                Find_default_tags( info, Pc_var_list, "server_" );
                Find_tags( info, &Config_line_list, "server_" );
        }

In the Fix_Rm_Rp_info code add:

        Find_tags( &Pc_entry_line_list, &PC_entry_line_list, "server_" );

Now we have an ADDITIONAL way of abusing configurations.

Any comments?

Patrick
Patrick Powell                 Astart Technologies,
[EMAIL PROTECTED]            9475 Chesapeake Drive, Suite D,
Network and System             San Diego, CA 92123
  Consulting                   858-874-6543 FAX 858-279-8424 
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.
-----------------------------------------------------------------------------

Reply via email to