I would suggest that you use CUPS. In your case, it probably makes more
sense than it might for some, but if you are deploying with Linux, and
MacOS, they already use CUPS and depending on your needs/network you may
want to just enable the CUPSBrowse support for advertising your printer
to others. The Windows clients should work about the same regardless of
the LP/CUPS decision. One other thing to note is that we are working
toward being able to make CUPS the default print service on Solaris and
possibly the only print service on Solaris somewhere down the line.
To make CUPS the "active" print service on your system you should run
# print-service -s cups
You may also want to logout and back in to make sure that your desktop
session isn't running the ospm-applet, which will attempt to
automatically configure LP queues when you attach printers.
If you plan on using a USB printer, you will want build 105 or later due to
6697318 printing to USB printer hangs under CUPS
-Norm
Ray Clark wrote:
> In trying to set up a print service I ran into many problems. I was using
> "Print Manager" because that was what was presented in the menus. I plan to
> start over.
>
> What print service should I run, lp or cups? I don't care if it is GUI or
> commandline, I just need to be able to make it work.
>
> I need a local printer queue that also accepts jobs from Linux, Windows, and
> MacOS over the network. I used to do this with Samba, Linux going through
> CUPS, and Windows and MacOS going through Samba.
>
> What do you suggest? Thank you.
>
> --Ray
>
