Hide Forgot
Default search base for automount (cn=automount,dc=example,dc=com) is not complete. As it is mentioned in the documentation, right in section "11.2.4. Configuring Automount", IPA does support locations and the default location is cn=default, therefore all base references should be to cn=<location>,cn=automount,dc=example,dc=com (cn=default,cn=automount,dc=example,dc=com by default). 11.2.4.3. Configuring auto.direct - the first two entries are created during installation process - the third entry should be created by ipa command (see ipa help automount - there are very good examples there) 11.2.4.4. Indirect Maps - considering the following item list, this should be probably modified: "These three entries provide: " - all code snippets should be replaced by ipa commands which create them (see ipa help automount - there are very good examples there)
(In reply to comment #0) > Default search base for automount (cn=automount,dc=example,dc=com) is not > complete. As it is mentioned in the documentation, right in section "11.2.4. > Configuring Automount", IPA does support locations and the default location is > cn=default, therefore all base references should be to > cn=<location>,cn=automount,dc=example,dc=com > (cn=default,cn=automount,dc=example,dc=com by default). Fixed. > > > 11.2.4.3. Configuring auto.direct > - the first two entries are created during installation process How does this work? This assumes that auto.direct already exists, which in turn means that autofs/nfs(?) is already installed and configured. Even so, afaict auto.direct has to be manually created. Further, doesn't this work on non-IPA managed hosts as well? In this case, the installation process won't have been performed at all. (Note: I'm still coming to terms with NFS, so explanations are helpful). We might need to update the "Assumptions" section. > - the third entry should be created by ipa command > (see ipa help automount - there are very good examples there) Again, this assumes that the ipa commands are available. If you're setting up automount, etc., on non-ipa managed machines, or UNIX, whatever, the ipa commands are not there. Perhaps this would be better expanded to include both? Can I have an example command, just to make sure I get it right? > > 11.2.4.4. Indirect Maps > - considering the following item list, this should be probably modified: "These > three entries provide: " > - all code snippets should be replaced by ipa commands which create them > (see ipa help automount - there are very good examples there) Looking into it, but again, any example commands more than welcome.
Suggested command sequence from rcrit: 1. Create a new location $ ipa automountlocation-add baltimore 2. Create a map for man pages $ ipa automountmap-add baltimore auto.man 3. Add our map to the location's auto.master on mount point /usr/man $ ipa automountkey-add baltimore auto.master --key=/usr/man --info=auto.man 4. Add an indirect mount man1 for the auto.man map $ ipa automountkey-add baltimore auto.man --key=man1 \ --info='nfsserver.example.com:/export/manpages/man1' Use the following command to create discrete files of how the configuration appears. This is useful if you perform file-based automount: $ ipa automountlocation-tofiles baltimore I'll try to get all this in and built asap.
Added as much as I could with provided info, rebuilt Fedora version and posted for devel review. Will revisit tomorrow morning for any updates.
Nothing yet. Setting to MODIFIED. Will brew and push to qA *very* shortly so we can get this material out.
Red_Hat_Enterprise_Linux-Enterprise_Identity_Management_Guide-96-web-en-US-0.7-30.el5 Updated from Jan's comments and discussion with rcrit on IRC. No requests for changes as a result of (identical) Fedora version.
Verified: Red_Hat_Enterprise_Linux-Enterprise_Identity_Management_Guide-6-web-en-US-0.7-35.el5