Created attachment 523650 [details]
1. Download the attachment.
2. Make sure tack changes is turned on. Edit > Changes > Record.
3. Make any changes to the doc.
4. Attach the file to the bug.
5. Reassign the bug to me (dlackey).
I care about accuracy, completeness, clarity, and organization.
Under the assumption that all references to Enterprise IPA will be addressed.
para. 1, missing "s" in "actively used by many system client."
para. 1. Not sure this is entirely correct, "Clients such as sudo only use netgroups to manage authentication." It can use netgroups but can also use just users and groups.
para. 2. NIS distributes more than just netgroup data. It can provide user, group, network, host, etc as well. IPA provides a NIS listener to provide a map for passwd, group and netgroup.
It should be mentioned that the --nisdomain option just controls the domain that will appear in the triple, not the domain that the NIS listener responds to.
An example of using ypcat might be handy:
# ipa netgroup-add --desc=test test
# ipa netgroup-add-member --hosts=ipa.example.com test
# ypcat -d example.com -h ipa.example.com netgroup
In the description you say it will add a map named auto.example but the example is for auto.master
ipa-host-net-manage just controls whether a netgroup is automatically created for a hostgroup or not. Regardless IPA should prevent a duplicate netgroup and hostgroup name to be created.
The ipa-nis-manage utility controls whether the NIS listener is configured or not. A restart of 389-ds is required whenever the state is changed.
Setting to ON_QA for review for 6.2.
This is a bulk change, so I'm not providing links at this time. If you need help finding the info, ping sunny-dee on #docs or email me.