We have some "public" printers that are usable by anyone on our network. There are two problems that we're running into with these printers, and I was wondering if anyone here had some suggestions.
1) We need the real FQDN, not the one that the machine reports in the control file. IP address would also be okay, if a little less convenient. If a Windows machine prints to the printer, the logs report the windows machine name (which can be anything), rather than the real hostname. Adding force_fqdn_hostname doesn't help. 2) We don't control the machines that are using these printers, which means we don't control the PPDs or print settings on client machines (that seems to be how most people handle it). We really want to force duplex on ALL print jobs. They're HP 8150 printers. "append_z=duplex" and setting duplex on the front of the printer catch generic postscript jobs where simplex/duplex isn't specified, but they don't catch jobs that are explicitly set to simplex (which is all of them from Windows and MacOS X, by default). I'm thinking that a sed script to change all of the PS files is my only option. Are there other tricks? -- "I can't give you a brain, so I'll give you a diploma" - The Great Oz ----------------------------------------------------------------------------- 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. -----------------------------------------------------------------------------
