#4051 Handle 389-ds centralized scripts
Closed: Fixed None Opened 10 years ago by rcritten.

389-ds is working on centralizing some of its now instance-specific scripts.

https://fedorahosted.org/389/ticket/528

and

http://port389.org/wiki/Design/Instance_Script_Improvements_1.3.1

This will affect at least backup and restore which uses the instance-specific scripts.

According to the 389-ds ticket the instance-specific scripts are still there for now, backwards compatibility I suppose, but we should probably switch to using the centralized ones.


We should just do it. We use them at least in backup and restore:

$ git grep ldif2db
ipaserver/install/ipa_restore.py:                self.ldif2db(instance, backend, online=options.online)
ipaserver/install/ipa_restore.py:    def ldif2db(self, instance, backend, online=True):
ipaserver/install/ipa_restore.py:            args = ['%s/ldif2db' % self.__find_scripts_dir(instance),
ipaserver/install/ipa_restore.py:                self.log.critical("ldif2db failed: %s" % stderr)

Also, please check if we still need to have the scripts generated at all:

INF_TEMPLATE = """
...
inst_dir=   /var/lib/dirsrv/scripts-$SERVERID
"""

master:

  • 4d05b5d Use 389-ds centralized scripts.

Metadata Update from @rcritten:
- Issue assigned to dkupka
- Issue set to the milestone: FreeIPA 4.2

7 years ago

Login to comment on this ticket.

Metadata