Narendra Kumar S.S writes: > The first argument to this function is 0x10. > But, the value that is actually passed is SYSID_ERR_BAD_YP_BINDINGS1 (whose > value is 0x13).
Or "should have been passed." > After looking at the putback of 4649122, exactly 3 more codes are added > above SYSID_ERR_BAD_YP_BINDINGS1. > So, previously its value was 0x10 and after the putback of 4649112, the > value is changed to 0x13. > I think, what you have figured out is 100% correct. Thanks. ;-} > > but somehow > > new versions of both sysiduilib and libnslib.so.1 (which both depend > > on that file) weren't delivered into the image you're using. > But, why is this so? Won't they compile the entire gate for each build? > > And how do we correct this now? They're both delivered via SUNWadmap, so I'd suspect that a misbegotten patch was applied here. Looking at patchstatus.sfbay, I see that CR 4649122 was delivered by patch IDs 119081-11 and 119252-09. Looking at that latter one, I see that it delivers /usr/sbin/sysiduilib but does *NOT* deliver the /usr/snadm/lib/libnsnis.so.1 that was also changed. "Oops." I think 119252 needs to be fixed, and may need to be bad-patched. It's broken. Surprisingly, even though this was broken back in the -09 version, the -15 version still has the same problem. Another issue to resolve here is how this sort of an error could have happened in the first place. Is the Install gate lacking the 'protcmp' and 'wsdiff' tools? I don't know how patches are validated there, but something slipped through the cracks. -- James Carlson, KISS Network <james.d.carlson at sun.com> Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
