Ghee Teo wrote:
Stewart Walters wrote:

Mind you in my situation, my CUPS server is situated on a Debian Linux box and CUPS on Opensolaris is configured with a /etc/cups/client.conf file pointing to it. While I don't think it has an affect, I haven't ruled it out yet either.
We don't use /etc/cups/client.conf to configure cups.
Actually, client.conf is a CUPS specific functionality.

The CUPS 1.4 documentation (http://www.cups.org/documentation.php/doc-1.4/sharing.html) states the following:

--- snip ---
Automatic Configuration using IPP

CUPS can be configured to run without a local spooler and send all jobs to a single server. However, if that server goes down then all printing will be disabled. Use this configuration only as absolutely necessary.

The default server is normally the local system ("localhost"). To override the default server create a file named /etc/cups/client.conf with a line as follows:

ServerName server
--- snip ---

It's a pretty common way to configure a multi server environment to send it's jobs to the dedicate "print server", and I already have had success in Production environments configuring CUPS with a client.conf on both Solaris 10 and Linux servers.

My current /etc/cups/client.conf has the following:

ServerName printserver.example.com:631

Having already put this configuration in place a long time ago, I've just run system-config-printer as you suggested and I already get an entire list of the print queues available on printserver.example.com (the debian box).

When I click on Server -> Settings, I'm asked for the root password of printserver.example.com. Once I type this in, the "Show Printers shared by other systems" is already enabled.

I already know using CUPS on OpenSolaris as a client to the Debian Linux works, as I can print from OpenSolaris Thunderbird successfully. I get this message box when attempting to print from Thunderbird: http://tinypic.com/r/2znsp4y/4

However Firefox and evince receive a printing dialog box like this: http://tinypic.com/r/jua9fn/4

P.S. This is the last thing I can advise apart from asking you to upgrade to a later build :)
I'd like to avoid this if possible, as this server is a Sun Ray server and I'm not yet sure how well it works with snv_125 or snv_126 yet (there are varying reports).

Regards,

Stewart
_______________________________________________
opensolaris-discuss mailing list
[email protected]

Reply via email to