cancel
Showing results for 
Search instead for 
Did you mean: 
huyvl3-fptcloud
Flight Engineer
Flight Engineer
  • 455 Views

Document RH134 describes an example of an incorrect use of wildcards in autofs

Document RH134 describes an example of an incorrect use of wildcards in autofs. Specifically, the * character will replace the & character in the /shares/& pattern. For example, work results in /shares/work, but the document mentions another path as /exports/work (see below)

====================== RH134 - Section 9.3 ======================

Wildcards in an Indirect Map

When an NFS server exports multiple subdirectories within a directory, then the automounter can be configured to access any of those subdirectories with a single mapping entry.

Continuing the previous example, if serverb:/shares exports two or more subdirectories, and they are accessible with the same mount options, then the content for the /etc/auto.demo file might appear as follows:

*  -rw,sync  serverb:/shares/&

The mount point (or key) is an asterisk character (*), and the subdirectory on the source location is an ampersand character (&). Everything else in the entry is the same.

When a user attempts to access /shares/work, the * key (which is work in this example) replaces the ampersand in the source location and serverb:/exports/work is mounted. As with the indirect example, the autofs service creates and removes the work directory automatically.

Labels (1)
0 Replies
Join the discussion
You must log in to join this conversation.