Files
freeipa/install
Misnyovszki Adam a1459e38e7 ipactl can not restart ipa services if current status is stopped
fixed by starting the directory server when restarting if it is not
currently running to enable fetching running services

later restart didn't check that

also added a check, that if the directory server started at the
beginning, there is no need to restart it

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

Reviewed-By: Martin Kosek <mkosek@redhat.com>
2014-02-19 17:47:57 +01:00
..
2014-01-21 12:05:09 +01:00
2014-01-03 09:46:05 +01:00
2014-01-21 12:24:54 +01:00
2013-05-06 16:22:30 +02:00
2014-01-21 12:04:02 +01: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.