Thanks for the tip. I will try it and let you know


[EMAIL PROTECTED] wrote:

> hmmm,
>
> I don't know precisely what's going on, but the controlfile is created 
> by the first instance that uses the lpr protocol and will not be 
> changed later...
>
> There is one other thing I thought about (I had some stupid problems 
> lately) are you sure the options don't get dropped by using "lp -d 
> PRINTER -o OPTIONS" perhaps "lp -o OPTIONS -d PRINTER" would be worth 
> a try ?
>
> regards
>         ~christoph
>  
>  
>  
>
> Michael Spicyn wrote:
>
>> Thanks Christopher
>>
>> That is precisly where my problem is burried. There are no Z options 
>> in control file.
>> I do not know whether "-a" options are discarded at origination point 
>> (ea Unixware) or at receiving point (ea Linux) or at LPRng level
>>
>> That is why I wanted to see what is being received before any 
>> processing takes place.
>>
>> Christoph Beyer wrote:
>>
>>>hi,
>>>
>>>you can stop the queue and take a look at the controlfile 'cfA...' in
>>>the spooldirectory. There should be a line 'Z<your option>' in it...
>>>
>>>regards
>>>             ~christoph
>>>
>>>
>>>
>>>Michael Spicyn schrieb:
>>>
>>>>I am running LPRng (v 3.6.26) on RH Linux v6.2. Users on remote UnixWare
>>>>v 7.1 are sending print job using ATT printing system.
>>>>The ATT printing system uses -o for option specifications.
>>>>
>>>>Unixware users user use:
>>>>        lp -d PRINTER -o OPTIONS
>>>>
>>>>I would like to see how print request and especially these -o OPTIONS
>>>>are arriving at Linux box.
>>>>
>>>>Unixware manuals are totally mute on the subject. My efforts with
>>>>prifix_o_to_z are ineffective. I suspect that UnixWare may not be
>>>>sending the -o options or might do it incorrectly (no that cannot be ;-)
>>>>) but I would like to be sure?
>>>>
>>>>Is there a way to see them?
>>>>
>>>>Thanks
>>>>
>>>>-----------------------------------------------------------------------------
>>>>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] <mailto:[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]
>>>> <mailto:[EMAIL PROTECTED]>with:                           | example:
>>>>subscribe LIST <mailaddr>       |  subscribe lprng-digest [EMAIL PROTECTED]
>>>> <mailto:[EMAIL PROTECTED]>unsubscribe LIST <mailaddr>     |  unsubscribe lprng 
>[EMAIL PROTECTED]
>>>>
>>>> <mailto:[EMAIL PROTECTED]>If you have major problems,  send email to 
>[EMAIL PROTECTED] <mailto:[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