freeipa/install
Stanislav Laznicka e9f0e9d8fa Decreased timeout for IO blocking for DS
Should fix the DS from going unresponsive in some cases

https://fedorahosted.org/freeipa/ticket/5383

Reviewed-By: Thierry Bordaz <tbordaz@redhat.com>
Reviewed-By: Martin Basti <mbasti@redhat.com>
2016-06-02 20:20:28 +02:00
..
certmonger Refactor ipautil.run 2015-12-14 10:54:23 +01:00
conf Increased mod_wsgi socket-timeout 2016-06-02 19:26:32 +02:00
ffextension webui: append network.negotiate-auth.trusted-uris 2014-09-11 09:41:51 +02:00
html Added warning to user for Internet Explorer 2016-04-28 14:28:11 +02:00
migration Remove unused imports 2015-12-23 07:59:22 +01:00
oddjob ipaplatform: Move remaining user/group constants to ipaplatform.constants. 2016-03-23 13:32:55 +01:00
po Fix URL for reporting bugs in strings 2016-03-01 15:26:52 +01:00
restart_scripts Move freeipa certmonger helpers to libexecdir. 2016-02-26 08:29:44 +01:00
share Added <my_hostname>=<IPA REALM> mapping to krb5.conf 2016-06-02 20:09:36 +02:00
tools Performance: Find commands: do not process members by default 2016-05-31 14:08:54 +02:00
ui Update the delete dialog on details user page 2016-06-02 18:42:06 +02:00
updates Decreased timeout for IO blocking for DS 2016-06-02 20:20:28 +02:00
wsgi Modernize 'except' clauses 2015-08-12 18:17:23 +02:00
configure.ac CONFIGURE: Replace obsolete macros 2016-03-08 20:02:27 +01:00
Makefile.am trusts: add support for one-way trust and switch to it by default 2015-07-08 01:56:52 +02:00
README.schema Add some basic rules for adding new schema 2010-08-27 13:40:37 -04:00

Ground rules on adding new schema

Brand new schema, particularly when written specifically for IPA, should be
added in share/*.ldif. Any new files need to be explicitly loaded in
ipaserver/install/dsinstance.py. These simply get copied directly into
the new instance schema directory.

Existing schema (e.g. in an LDAP draft) may either be added as a separate
ldif in share or as an update in the updates directory. The advantage of
adding the schema as an update is if 389-ds ever adds the schema then the
installation won't fail due to existing schema failing to load during
bootstrap.

If the new schema requires a new container then this should be added
to install/bootstrap-template.ldif.