Re: [zones-discuss] [Fwd: Cloned zones and printers - redux]
On 10/31/07, Norm Jacobs [EMAIL PROTECTED] wrote: Mike Gerdts wrote: It seems as though printers.conf could point to localhost in the master zone and the clones would then also point to their respective selves. Is there something broken with that approach? Not that we don't see it, but we don't recommend configuring more than one system (or zone in your situation) as a print server for a network attached printer. Doing so can cause starvation and doesn't provide you with an accurate view of the print queue because there are multiple queues feeding the device. The bottom line there is that you can end up submitting a print job, appear to be printing or ready to print and sit there while other systems (or zones) are busy printing copies of the phone book. Every time you check the queue, you are either printing or waiting for the device, but the activity on the device is invisible to your system or zone. Now, if the printer in question isn't going to be particularly busy or is only really used by a small number of people, it's not a real problem. In the general case, I agree with you. This, however, is something more of an enterprise print architecture argument rather than addressing the zone configuration. There are cases where a local print queues for the same physical printer may be appropriate. For example, if I have a node-locked licensed application that prints in a format that is not understood by the printer, the local print queue may act as a filter that translates to PS or PCL then forwards to a traditional print server that feeds print jobs to the real printer. If the print server does not have a license for the app (or is otherwise incapable of running the app), it may not be able to use the application to do the file conversion. Several years back I dealt with engineering apps that would generate 100's of pages of garbage if File-Print was used. If the print queue recognized the print job format and put it through the right filter (that called the app in command line mode to do a conversion) it would print a nice single page drawing. -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] [Fwd: Cloned zones and printers - redux]
I'm not on zones-discuss, but this was forwarded to me. It sounds like you created a local print queue for your network attached printer in your source zone. When you clone that zone, the printers.conf file entry in the new zone references the hostname of the source zone, so the print commands try and contact the print service in the source zone instead of the current zone. You can fix this by configuring a queue for your printer in the global zone (or on another system) and then configuring access to the remote queue. -Norm Subject: [zones-discuss] Cloned zones and printers - redux From: Phil Freund [EMAIL PROTECTED] Date: Tue, 30 Oct 2007 11:59:47 -0700 (PDT) To: zones-discuss@opensolaris.org To: zones-discuss@opensolaris.org Let's try this again. Maybe someone won't hijack this thread this time. I just ran across an odd issue. I have a default network printer I setup for all of my zones. I added that printer to the zone I use as a source for cloning new zones with no problem and it prints fine. I can create new zones from the source zone that has the printer defined in it with no problem. Now here's the oddity: As long as the original source zone is booted, I can print to the printer that was in the original source zone. If the source zone is shutdown, I cannot print to that printer and the print request hangs in the queue. As a matter of fact, if I issue lpstat -o with the source zone up, it returns immediately but if the source zone is down, the lpstat -o command waits at least 30 seconds to respond. If I delete the printer from the new zone and re-add it, it works normally without any dependency on the source zone. Does anyone have any ideas about why this is happening? If this is expected behavior, shouldn't it be documented somewhere with a warning? Phil This message posted from opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org ___ zones-discuss mailing list zones-discuss@opensolaris.org
Re: [zones-discuss] [Fwd: Cloned zones and printers - redux]
On 10/30/07, Norm Jacobs [EMAIL PROTECTED] wrote: I'm not on zones-discuss, but this was forwarded to me. It sounds like you created a local print queue for your network attached printer in your source zone. When you clone that zone, the printers.conf file entry in the new zone references the hostname of the source zone, so the print commands try and contact the print service in the source zone instead of the current zone. You can fix this by configuring a queue for your printer in the global zone (or on another system) and then configuring access to the remote queue. It seems as though printers.conf could point to localhost in the master zone and the clones would then also point to their respective selves. Is there something broken with that approach? -- Mike Gerdts http://mgerdts.blogspot.com/ ___ zones-discuss mailing list zones-discuss@opensolaris.org
