On Sun, 5 May 2002, Patrick Powell wrote: > > > > 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... >
I can't see it realy makes much differenct from using the "server" and "client" keyword. > 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. > The problem arises, I beleive, because both lpr and lpd contains the same capabilities to talk to a remote lpd server and thus needs the same set of printcap parameters. If "force_localhost" is NOT in effect there is no confusion as only the lpr (and lpq and lprm) is in the picture as the lpd daemon would be bypassed entirely. Therefor in that case all the printcap parameter applies to the lpr program. If "force_localhost" IS in effect, then the behaviour of lpd is radically changed, as it is always talking to the lpd daemon via "localhost" or perhaps via a unix (local) socket. Therefore most if not all the parameters in the printcap entry applies to the lpd daemons and not to the lpr program. If, you still need to have a printcap parameter apply to lpr in this case you can still add the "client" keyword to a separate stanca. I wonder if you can use that to "force_localhost" to determine if a printcap parameter applies to lpr/lpq/lprm or not, or if it would create problems if you made such a rule. "force_localhost" will always be in effect unless you either have rm=hhh and rp=xxx combination or lp=xxx@hhh defined in the printcap entry. BTW, the server client destinction is not entirely correct, as the lpd daemon works both as a server and as a client, a server when a lpr or another lpd daemon is sending a printrequest, and as a client when it sends a print request to another lpd server. That does not mean that you should change the labels as that would just cause unnecessary extra confusion. Villy ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
