freeipa/install/tools/man/Makefile.am

# This file will be processed with automake-1.7 to create Makefile.in

AUTOMAKE_OPTIONS = 1.7

NULL=

man1_MANS = 				\
	ipa-replica-conncheck.1		\
	ipa-replica-install.1		\
	ipa-replica-manage.1		\
	ipa-csreplica-manage.1		\
	ipa-replica-prepare.1		\
	ipa-server-certinstall.1	\
	ipa-server-install.1		\
	ipa-dns-install.1		\
	ipa-ca-install.1		\
	ipa-ldap-updater.1		\
	ipa-compat-manage.1		\
	ipa-nis-manage.1		\
	ipa-host-net-manage.1		\
	ipa-compliance.1

man8_MANS =				\
	ipactl.8			\
        $(NULL)

install-data-hook:
	@for i in $(man1_MANS) ; do gzip -f $(DESTDIR)$(man1dir)/$$i ; done
	@for i in $(man8_MANS) ; do gzip -f $(DESTDIR)$(man8dir)/$$i ; done

MAINTAINERCLEANFILES =          \
        Makefile.in             \
        $(NULL)
Add some missing man pages 436501 2008-03-17 17:04:49 -05:00			`# This file will be processed with automake-1.7 to create Makefile.in`

			`AUTOMAKE_OPTIONS = 1.7`

Second half of the redoing how the version is managed. 2008-05-05 14:25:28 -05:00			`NULL=`

Add some missing man pages 436501 2008-03-17 17:04:49 -05:00			`man1_MANS = \`
Connection check program for replica installation When connection between a master machine and future replica is not sane, the replica installation may fail unexpectedly with inconvenient error messages. One common problem is misconfigured firewall. This patch adds a program ipa-replica-conncheck which tests the connection using the following procedure: 1) Execute the on-replica check testing the connection to master 2) Open required ports on local machine 3) Ask user to run the on-master part of the check OR run it automatically: a) kinit to master as default admin user with given password b) run the on-master part using ssh 4) When master part is executed, it checks connection back to the replica and prints the check result This program is run by ipa-replica-install as mandatory part. It can, however, be skipped using --skip-conncheck option. ipa-replica-install now requires password for admin user to run the command on remote master. https://fedorahosted.org/freeipa/ticket/1107 2011-05-22 12:17:07 -05:00			`ipa-replica-conncheck.1 \`
Add some missing man pages 436501 2008-03-17 17:04:49 -05:00			`ipa-replica-install.1 \`
			`ipa-replica-manage.1 \`
Create tool to manage dogtag replication agreements For the most part the existing replication code worked with the following exceptions: - Added more port options - It assumed that initial connections were done to an SSL port. Added ability to use startTLS - It assumed that the name of the agreement was the same on both sides. In dogtag one is marked as master and one as clone. A new option is added, master, the determines which side we're working on or None if it isn't a dogtag agreement. - Don't set the attribute exclude list on dogtag agreements - dogtag doesn't set a schedule by default (which is actually recommended by 389-ds). This causes problems when doing a force-sync though so if one is done we set a schedule to run all the time. Otherwise the temporary schedule can't be removed (LDAP operations error). https://fedorahosted.org/freeipa/ticket/1250 2011-07-14 22:35:01 -05:00			`ipa-csreplica-manage.1 \`
Add some missing man pages 436501 2008-03-17 17:04:49 -05:00			`ipa-replica-prepare.1 \`
			`ipa-server-certinstall.1 \`
Sort updates by DN length and by default process all files in the updates dir. The updates directory is currently hardcoded to /usr/share/ipa/updates. All of the files are read into memory and then sorted by the length of the DN. This is so we can be sure that parent entries are added before children. Also add a man page. 2008-09-12 17:40:26 -05:00			`ipa-server-install.1 \`
Ship the ipa-dns-install man page ticket 734 2011-01-10 09:37:45 -06:00			`ipa-dns-install.1 \`
Make dogtag an optional (and default un-) installed component in a replica. A dogtag replica file is created as usual. When the replica is installed dogtag is optional and not installed by default. Adding the --setup-ca option will configure it when the replica is installed. A new tool ipa-ca-install will configure dogtag if it wasn't configured when the replica was initially installed. This moves a fair bit of code out of ipa-replica-install into installutils and cainstance to avoid duplication. https://fedorahosted.org/freeipa/ticket/1251 2011-06-17 15:47:39 -05:00			`ipa-ca-install.1 \`
New tool to enable/disable DS plugin to act as NIS server 2009-05-07 09:51:44 -05:00			`ipa-ldap-updater.1 \`
			`ipa-compat-manage.1 \`
managed entry hostgroup netgroup support https://fedorahosted.org/freeipa/ticket/543 2010-12-10 17:21:39 -06:00			`ipa-nis-manage.1 \`
Add support for tracking and counting entitlements Adds a plugin, entitle, to register to the entitlement server, consume entitlements and to count and track them. It is also possible to import an entitlement certificate (if for example the remote entitlement server is unaviailable). This uses the candlepin server from https://fedorahosted.org/candlepin/wiki for entitlements. Add a cron job to validate the entitlement status and syslog the results. tickets 28, 79, 278 2011-02-01 13:24:46 -06:00			`ipa-host-net-manage.1 \`
			`ipa-compliance.1`
Add some missing man pages 436501 2008-03-17 17:04:49 -05:00
			`man8_MANS = \`
			`ipactl.8 \`
Get merged tree into an installalble state. I have only tested the all, rpms and *clean targets directly. install may work but the rpm moves a lot of things around for us. The Apache configuration file isn't in its final state but it works with the new mod_python configuration. 2009-02-02 12:50:53 -06:00			`$(NULL)`
Add some missing man pages 436501 2008-03-17 17:04:49 -05:00
			`install-data-hook:`
			`@for i in $(man1_MANS) ; do gzip -f $(DESTDIR)$(man1dir)/$$i ; done`
			`@for i in $(man8_MANS) ; do gzip -f $(DESTDIR)$(man8dir)/$$i ; done`
Second half of the redoing how the version is managed. 2008-05-05 14:25:28 -05:00
			`MAINTAINERCLEANFILES = \`
			`Makefile.in \`
			`$(NULL)`