<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
Brian K. Jones wrote:
<blockquote cite="mid200506201410.15194.jonesy.fds@CS.Princeton.EDU"
type="cite">
<pre wrap="">On Monday 20 June 2005 2:03 pm, Mike Jackson wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Don't put schema into 99user.ldif, it's not maintainable.
</pre>
</blockquote>
<pre wrap=""><!---->
This would seem to be contrary to the documentation on redhat's site. I'm
certainly not meaning to say you're wrong - quite the contrary - I'm pointing
out to whomever it may concern that the docs need polishing :)
</pre>
</blockquote>
99user.ldif is for schema that is added over LDAP. However, whatever
is in the file at start up will remain there through other restarts.
But in general, it's best to keep user defined schema in files named
60x.ldif through 98x.ldif.<br>
<blockquote cite="mid200506201410.15194.jonesy.fds@CS.Princeton.EDU"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Instead, create a file like 90myOwnSchema.ldif, then you can version
control and upgrade it when needed.
</pre>
</blockquote>
<pre wrap=""><!---->
I've also seen the docs mention that these files are imported in order, so I
understand, and will change this. Presumably, I can do a simple "mv" on the
file. Lemme know if this is not the case.
</pre>
</blockquote>
Sure. Just make sure there is nothing else in 99user.ldif that was
added over LDAP.<br>
<blockquote cite="mid200506201410.15194.jonesy.fds@CS.Princeton.EDU"
type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">Also, you should read about the silent installation capability of the
</pre>
</blockquote>
<pre wrap=""><!---->
I did. Thanks!
</pre>
<blockquote type="cite">
<pre wrap="">setup program. I have done extensive coding to generate silent.inf files
</pre>
</blockquote>
<pre wrap=""><!---->
Seen 'em, thanks!
</pre>
<blockquote type="cite">
<pre wrap="">from arbitrary data sources, and have automated the entire installatoin
and replicaton configuration process from start to finish.
</pre>
</blockquote>
<pre wrap=""><!---->
Right - and I plan to use this in the future to make disaster recovery, moving
of services/machines as simple and brainless as humanly possible. The first
step, though, was to get the import right before I go automating it ;-)
Did any of your coding allow for a "userSchema" keyword in the config file,
for which I could've just put the path to my schema file? That would be nice,
but I don't remember seeing it. I did see that I could specify an ldif file,
but attempts to put schema extensions in that ldif file have, so far, failed.
</pre>
</blockquote>
No. But that would be a nice enhancement.<br>
<blockquote cite="mid200506201410.15194.jonesy.fds@CS.Princeton.EDU"
type="cite">
<pre wrap="">
thanks,
brian.
</pre>
<blockquote type="cite">
<pre wrap="">--
mike
--
Fedora-directory-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Fedora-directory-users@redhat.com">Fedora-directory-users@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/fedora-directory-users">https://www.redhat.com/mailman/listinfo/fedora-directory-users</a>
</pre>
</blockquote>
<pre wrap=""><!---->
--
Fedora-directory-users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Fedora-directory-users@redhat.com">Fedora-directory-users@redhat.com</a>
<a class="moz-txt-link-freetext" href="https://www.redhat.com/mailman/listinfo/fedora-directory-users">https://www.redhat.com/mailman/listinfo/fedora-directory-users</a>
</pre>
</blockquote>
</body>
</html>