Bill Shannon wrote:
> Norm Jacobs wrote:
>>
>> Bill Shannon wrote:
>>
>>> We are planning to move to CUPS, but want to integrate support for
>>> various Solaris features before we dump LP.
>>
>> Like what?
RBAC, Trusted printing, SunRay attached printers, possibly pre-printed
media (lp forms)
>
>>> When I use Print Manager to add a new network printer using the BSD
>>> protocol, I get a printers.conf entry that looks like:
>>>
>>> lp2:\
>>> :printer-uri-supported=ipp\://nissan2/printers/lp2:\
>>> :bsdaddr=nissan2,lp2,Solaris:
>>>
>>> where "nissan2" is the machine on which I ran Print Manager, not the
>>> name of the remote machine that I entered in the dialog.
>>>
>>> This just seems completely broken. Is this a known problem?
>>>
>> If you added a "New Network Printer" in the Solaris Print Manager, it
>> would create a local print queue and you would see the local hostname
>> as the server name in the printers.conf data. If you "Add Access to
>> Printer", it should point to a remote print server in the
>> printers.conf data.
>
> I don't understand. Does "new network printer" really mean
> "new local printer that can be accessed by other machines over
> the network"? I thought I would add a new local printer and then
> manage access to it.
"new network printer" means a physical printer that you communicate with
over the network, but still need local queuing and filtering support.
The queue that gets created on the local system can be used by others to
print to the device, assuming that the rfc1179 and/or ipp-listener
services are running. At that point, other machines can "Add access to
printer"and point to the system that you created a queue on.
-Norm
