[31/Jan/2006:17:18:32 -0500] dse - The entry cn=schema in file /opt/fedora-ds/slapd-auspice/config/schema/63nisDomain.ldif is invalid, error code 20 (Type or value exists) - attribute type nisDomain: Does not match the OID "1.3.6.1.4.1.1.1.1.12". Another attribute type is already using the name or OID. 63nisDomain.ldif is (put in to support Solaris client): dn: cn=schema attributeTypes: ( 1.3.6.1.1.1.1.28 NAME 'nisPublickey' DESC 'nisPublickey' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) attributeTypes: ( 1.3.6.1.1.1.1.29 NAME 'nisSecretkey' DESC 'nisSecretkey' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) attributeTypes: ( 1.3.6.1.4.1.1.1.1.12 SUP name NAME 'nisDomain' DESC 'NIS domain' SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) attributeTypes: ( 2.16.840.1.113730.3.1.30 NAME 'mgrpRFC822MailMember' DESC 'mgrpRFC822MailMember' EQUALITY caseIgnoreIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) attributeTypes: ( 1.3.6.1.4.1.42.2.27.1.1.12 NAME 'nisNetIdUser' DESC 'nisNetIdUser' EQUALITY caseExactIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) attributeTypes: ( 1.3.6.1.4.1.42.2.27.1.1.13 NAME 'nisNetIdGroup' DESC 'nisNetIdGroup' EQUALITY caseExactIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) attributeTypes: ( 1.3.6.1.4.1.42.2.27.1.1.14 NAME 'nisNetIdHost' DESC 'nisNetIdHost' EQUALITY caseExactIA5Match SYNTAX 1.3.6.1.4.1.1466.115.121.1.26 ) objectClasses: ( 1.3.6.1.1.1.2.14 NAME 'NisKeyObject' DESC 'NisKeyObject' SUP top MUST ( cn $ nisPublickey $ nisSecretkey ) MAY ( uidNumber $ description ) ) objectClasses: ( 1.3.1.6.1.1.1.2.15 NAME 'nisDomainObject' DESC 'nisDomainObject' SUP top AUXILIARY MUST ( nisDomain ) ) objectClasses: ( 2.16.840.1.113730.3.2.4 NAME 'mailGroup' DESC 'mailGroup' SUP top MUST ( mail ) MAY ( cn $ mgrpRFC822MailMember ) ) objectClasses: ( 1.3.6.1.4.1.42.2.27.1.2.6 NAME 'nisNetId' DESC 'nisNetId' SUP top MUST ( cn ) MAY ( nisNetIdUser $ nisNetIdGroup $ nisNetIdHost ) ) ~ Can I get away with removing the oid from one of the files? Not sure how touchy schema files are about where what is defined. Richard Megginson wrote: > Roger Spencer wrote: > >> I dug the below out from the archive. Is there anything new on the >> subject? >> >> I've seemed to have slammed head first into the subject. Got SUSE >> and RHEL 3 using nisObjects happily (apparently they'll support >> either model). Just configured a Solaris 10 box as a client and it >> wants automountMap. Even worse, Solaris 9 and 10 do automountMap, >> Solaris 8 does nisObjects. Fortunately, I have all three versions >> running. (Info on Solaris' automount: >> http://www.informit.com/articles/article.asp?p=31550&seqNum=4&rl=1 ) >> >> I tried loading the 10rfc2307bis.ldif (by replacing the >> 10rfc2307.ldif file) and slapd wouldn't restart. > > What errors did you see in the errors log? > >> >> Any idea to a) get the automountMap objects in the schema? b) >> possibly support both models? >> >> * /From/: Rich Megginson <rmeggins redhat com> >> * /To/: "General discussion list for the Fedora Directory server >> project." <fedora-directory-users redhat com> >> * /Subject/: Re: Re: automount >> * /Date/: Tue, 16 Aug 2005 09:01:40 -0600 >> >> ------------------------------------------------------------------------ >> There has been a lot of confusion around this issue (mostly on my >> part). I think one of the problems is that rfc2307 support from OS >> vendors is now deprecated in favor of rfc2307bis >> http://www.ietf.org/internet-drafts/draft-howard-rfc2307bis-01.txt, >> which is still in Internet Draft phase (and is due to expire very >> quickly). A new draft is being worked on with the goal of generating >> a new RFC. The bis draft has one problem with it, in that it requires >> the use of the authPassword attribute (defined in RFC 3112 >> http://www.ietf.org/rfc/rfc3112.txt). FDS does not support this (and >> neither does OpenLDAP AFAICT). I have attached a file called >> 10rfc2307bis.ldif. This is the schema from the 2307bis I-D in FDS >> schema format. >> >> The preferred way to map the automount information is to use the >> automount attributes and objectclasses in the RFC 2307bis draft >> schema. The problem is that I don't know all of the vendor support. >> So far I've been unable to find out what RHEL3 and RHEL4 support. >> I've been told that Solaris has support for the bis schema. >> >> If you like, you can replace the 10rfc2307.ldif schema supplied with >> FDS with the attached file, and see what happens. >> >> >> ------------------------------------------------------------------------ >> >> -- >> Fedora-directory-users mailing list >> Fedora-directory-users at redhat.com >> https://www.redhat.com/mailman/listinfo/fedora-directory-users >> >> > ------------------------------------------------------------------------ > > -- > Fedora-directory-users mailing list > Fedora-directory-users at redhat.com > https://www.redhat.com/mailman/listinfo/fedora-directory-users > -------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20060131/e3fe941b/attachment.html
