> The information used to determine if a remote queue
> is accepting doesn't
> come across the wire when you query a system using
> rfc1179. Sometimes,
> you can infer it, but not always. In the past we
> simply lied to the
> users and told them that the queue was accepting.
> Perhaps we should
> continue with that lie.
What ever option we go for I guess a better message for clients is needed,
since
% lpstat -a printername
ps133 not accepting requests since Tue Mar 13 14:19:35 2007
unknown reason
Is giving the wrong information in one way or another (best not to give any
thing than the wrong information)
> > (2) Using ldap display errors and fails
> The "printer-uri" in LDAP is likely to be the
> problem. Solaris Nevada
> uses a
> "printer-uri-supported" attribute to determine how to
> communicate with
> the print service about a queue. There is some code
> that converts
> "printer-uri" to "printer-uri-supported" that's
> likely to be causing you
> some problems. If you add a "printer-uri-supported"
> attribute to LDAP,
> with a correct printer-uri-supported value, it should
> work:
>
> Ex:
> # lpset -n ldap -a
> inter-uri-supported=lpd://lpserver/printers/ps133#Sola
> ris ps133
It seems to work and it also works on previous version of Solaris, so I can
switch over the ldap version with out upsetting all users.
Thanks
This message posted from opensolaris.org
