schema extension via ldif at install time

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Actually, I figured it out, and just performed an install that worked. 

I put my 99user.ldif in /opt/fedora-ds/bin/slapd/install/schema before running 
setup. Then, when I ran setup, I selected "custom install". Then I just fed 
it my ldif dump from openldap, and there were no errors in the ldif import 
stage of the installation. If I find that things really didn't happen after I 
fire up the console, I'll check back, but all appears well at the moment. 

brian.

On Monday 20 June 2005 1:26 pm, David Boreham wrote:
> Brian K. Jones wrote:
> >I want to perform a custom installation of FDS, and when it asks for the
> > ldif file to be imported, I want to point it at a file that contains ldif
> > to extend the schema, and add the entries dumped from my old openldap
> > directory.
> >
> >Without extending the schema, the import will fail because every entry
> >violates the default schema. However, turning schema checking off leaves
> > some small chance that there is something in my directory that shouldn't
> > be there or isn't as it should be.
> >
> >I have another installation of FDS on a test machine, and I used the GUI
> > to add my extra objects and attributes, and I tried copying the resulting
> > ldif to the server I'm now trying to install (minus operational stuff),
> > but the install ignored the cn=schema part of my LDIF file (the part
> > holding the schema extensions), and subsequently, all of the entries
> > failed.
> >
> >Has anyone done this? Any clues? Is there somewhere I can place a
> > 99user.ldif file *before* running setup that will cause the slapd
> > instance to use it the first time it starts up?
>
> I'm not sure if there's a 'clean' way to do what you want (there may be,
> I'm not terribly familiar with the details of installation), however I
> suspect
> that the reason it's not working for you is that the ldif file is
> _imported_,
> and not added via LDAP. You can't import schema entries because they
> don't live in an importable back end. They need to be added via an
> LDAP connection.
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users at redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users




[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux