Please create a bug and attach your (zipped) gibberish file. Bad schema
should be logged (at least) - assuming the gibberish didn't actually
form a valid schema component some how.
Brian Rudy wrote:
I did some additional digging and realized that somehow I did
something incorrectly while converting the samba.schema file to
61samba.ldif. My 61samba.ldif was over 176kb (the latter part being
filled with binary gibberish), but should have been ~13k if things had
completed properly :P Strangely enough, I didn't see any errors in the
slapd logs about being unable to load the schema file...
Brian Rudy wrote:
> Pete Rowley wrote:
>
>> Brian Rudy wrote:
>>
>>>
>>> I double checked
>>> /opt/fedora-ds/slapd-<server>/config/schema/61samba.ldif created in
>>> the initial setup steps and was unable to find a sambaUnixIDPool
>>> objectclass, but did see a sambaUnixIdPool.
>>
>>
>>
>>
>> These two values /should/ be equivalent.
>>
>>> Any idea of what might be happening here?
>>
>>
>>
>>
>> Did you restart the server after you initially added the new schema
>> files?
>
>
>
> I did indeed. It almost looks like 61samba.ldif isn't being used for
> some reason...
>
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users(a)redhat.com
>
https://www.redhat.com/mailman/listinfo/fedora-directory-users
--
Fedora-directory-users mailing list
Fedora-directory-users(a)redhat.com
https://www.redhat.com/mailman/listinfo/fedora-directory-users