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
Mike Gerdts wrote:
> 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
>>
That seems reasonable to me too but it would require a change in the lpadmin
command to setup the printers.conf entries with localhost instead of the
server name - or of course, manually editing printers.conf once the printers
are built. I'd have to test to see if using localhost would break pr
That explains where the problem lies with cloning the zone: The cloning
function doesn't correctly update the content of the printers.conf file so that
those entries which reference the source zone name get changed to the new clone
name. That's a bug. Until it gets fixed, I'll just have to make
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 refere
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 comman
