Hi
I strongly suspect that somehow updatemanager has created some
inconsistency.
If the old BE list pam.conf as type e pamconf in /var/sadm/install/contents
Then as long as the pspool/pkgmap is also e pamconf this should just
install.
Perhaps grep for pam.conf in
SUNWcsr pkgmap defines /etc/pam.conf as a 'e' (editable) type file with a class
action script 'pamconf'. In this situation, when you install a new zone, when
it comes to install the SUNWcsr package, the class action script will just copy
the file from /var/sadm/pkg/SUNWcsr/save/... to
Thanks for the reply.
I'm digging through i.pamconf to find out why its not copying the file.
This seems to be the problem. Its doing the editing, but not the
initial copy of the file. I checked the CLEANUP_FILE and found that
it had logged messages default entries updated, which means it is
Hi,
I'm still having zone creation issues where my /etc/pam.conf is corrupt.
I have 2 machines, one works fine, the other always creates the
zone with a bad /etc/pam.conf.
I used the Dtrace toolkit opensnoop program to watch on both machines.
I see on the good machine, where it creates the
