/var/sadm/pkg/SUNWcsr/save/pspool/SUNWcsr/reloc/etc/pam.conf
and /etc/pam.conf in the global zone are identical.
Just the ones in the new local zone get stripped down and the
entries are out of order.
Renaud Manus wrote:
The /etc/pam.conf in the non-global zone is a copy of
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
Jan Hendrik Mangold writes:
I am programatically creating zones and just realized that they all have the
same fingerprint in /etc/zones/index. The zones are created from the same
template in /etc/zones
Is that correct or should I be worried?
If the 'fingerprint' you're referring to is the
I have three SAP database instances/central instances running in three sparse
zones with no problem.
I have created a new sparse zone for a new SAP installation (Solution Manager
4.0) and started the installation. SAP requires a 1.4.2 SDK even though Java
1.5 comes with Solaris 10. The 1.4.2
Hi,
Is this the recommended solution ?
In the Global zone, there is already a copy of JDK installed (by default
in Solaris 10). All the java links are setup properly in /usr.
However, as this is a sparse zone, /usr is inherited i.e. read-only.
Installing JDK anywhere in the sparse zone, while
Yes, the technique or reinstalling a new JDK in a local file system in the
sparse zone (in my case I installed it in /usr/local/bin) where you have write
permissions worked just fine. The down side was that I already had a working
JDK in both the global zone and the sparse zone. I installed
