I'm using Solaris 10 U2.

I've been manually copying the GZ's /etc/pam.conf to the local zone,
however I'd like to get to the root of the problem rather than kludge this.
I just don't have the "warm and fuzzy feeling" about the zones created.
I was hoping that if I can get to the root of the problem I may uncover
other things that may be going wrong.  I'm sure it must have something
to do with the failed patch installations from "updatemanager".

Jeff Victor wrote:

If you are using Solaris Express, you may be able to use "zoneadm ... clone ..." to achieve this goal.

If not, you can add a line to your zone-creation script which copies the GZ's /etc/pam.conf file to $zonepath/root/etc/pam.conf .

Brian Kolaci wrote:

I had an issue in the past with patches when a zone couldn't boot
to have the patches install properly.  The zonepath got blown away.
I then destroyed the zones and retried the patching, which appeared
to work.

Now whenever I create zones the /etc/pam.conf file is missing
several entries, including the "login" and many others.  In order
to be able to "zlogin" into the zone I need to manually update
the /etc/pam.conf of each local zone from the global zone.

How do I fix my installation so that zone creation works properly
and I get the proper /etc/pam.conf generated?

Is there any way to validate the global zone to see what packages
may be corrupt or have bad metadata?

zones-discuss mailing list

Reply via email to