I'm in the process of opening a case with Sun support as well, but thought I'd
post here to see if I get a quicker / different response.
I'm running SaMBa 3.025 - bundled in Solaris 10 U4 in a container.
The container has a primary dns name as well as 2 aliases.
I configure the /etc/krb5/krb5.co
I have resolved the issue. The resolution itself raises several questions, but
as I am on a deadline, I'll leave those to others.
touch /etc/krb5.keytab
that's the trick.
that's the fix.
the smb.conf file was not configured to use kerberos keytab, but apparently it
was trying to.
This me
The idea has merit, although I'm not sure you can't get most of this effect
with big zones, and careful application of patches and packages.
Although, an entirely automated form of this as a branded zone would give would
be great. Yes, we have to manage patches independently, and have to do
u
We were getting hit by developers constantly asking for "what box is hosting
our container xyz?"
We kept telling them it doesn't matter (all the boxes hosting containers are
the same - at least for now).
We sent them spreadsheets with the mappings of global-zone host to
non-global-zones.
None o
