On Oct 10, 2009, at 18:32 , Kevin Kammer wrote: > I am forwarding this thread to the kerberos-discuss list, as per your > recommendation... > >> I'm glad we could help, Kevin. I'll let everyone know. >> One of the engineers suggested you share your problem on >> kerberos-discuss at opensolaris.org. That will give you access >> to most of the people whom I got to review your problem. >> >> Jim > > Kevin Kammer wrote: >> Mr. Siwila: >> >> Thanks, your advice certainly seems to have hit the nail on the head. >> Having installed SUNWgssc in the zone, the kadmin service runs >> without >> complaining. I don't know if I ever would have figured that out on my >> own; or, to quote the bug report, "This problem is very difficult for >> admins to diagnose." I second that! Might I assume that at some >> point in >> the future, SUNWgssc might be registered as a dependency of SUNWkdc?
I've already filed http://defect.opensolaris.org/bz/show_bug.cgi?id=11823 which covers this. Hopefully this will be fixed in the near future. >> >> There may be other bugs at work here, if as you say, the acl >> warning is >> not supposed to kill kadmind. In my case, it certainly did. The acl warning is just that: a warning. In this case it is bogus and needs to be fixed. This is filed as: 6889618 kadmind prints bogus acl warning (its not showing up on bugs.opensolaris.org but I guess it will soon) >> However, at >> first glance, installing SUNWgssc seems to have fixed that. The two are not related. The warning isn't fatal, not having SUNWgssc installed is what caused the failure. -M -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://mail.opensolaris.org/pipermail/kerberos-discuss/attachments/20091010/9b23bedc/attachment.html>
