freeipa

0 Fork 0

Files

T

Petr Viktorin 0ca29fac9a Move install script error handling to a common function

All of our install/admin scripts had a try/except block calling the
main function and handling common exceptions. These were copy-pasted
from each other and modified to various levels of sophistication.
This refactors them out of installers to a single function, which
includes a final pass/fail message for all of the scripts.

Non-install scripts that set up the same log handler levels for
stderr and log file are not changed, as it's not possible to log
to only the logfile without changing the logger configuration.

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

2012-05-31 14:37:27 +02:00

conf

Implement password based session login

2012-02-27 05:57:43 -05:00

html

Fixed inconsistent image names.

2011-10-27 14:05:12 +00:00

migration

Forms based authentication UI

2012-03-02 11:04:33 +01:00

validate i18n strings when running "make lint"

2012-04-26 13:53:37 +02:00

restart_scripts

Configure certmonger to execute restart scripts on renewal.

2012-04-10 01:08:41 -04:00

- add a pair of ethers maps for computers with hardware addresses on file

2012-04-26 09:00:22 +02:00

tools

Move install script error handling to a common function

2012-05-31 14:37:27 +02:00

Correction of nested search facets tab labels

2012-05-15 13:06:06 +02:00

updates

- add a pair of ethers maps for computers with hardware addresses on file

2012-04-26 09:00:22 +02:00

configure.ac

Configure certmonger to execute restart scripts on renewal.

2012-04-10 01:08:41 -04:00

Makefile.am

Configure certmonger to execute restart scripts on renewal.

2012-04-10 01:08:41 -04:00

README.schema

Add some basic rules for adding new schema

2010-08-27 13:40:37 -04:00

README.schema

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.