Print this page
6198 Let's EOL cachefs


  99 
 100 
 101        -v
 102                       Verbose mode. Notifies of autofs mounts, unmounts, or
 103                       other non-essential information.
 104 
 105 
 106 USAGE
 107    Map Entry Format
 108        A simple map entry (mapping) takes the form:
 109 
 110          key [ -mount-options ] location ...
 111 
 112 
 113 
 114 
 115        where key is the full pathname of the directory to mount when used in a
 116        direct map, or the simple name of a subdirectory in an indirect map.
 117        mount-options is a comma-separated list of mount options, and location
 118        specifies a file system from which the directory may be mounted.  In
 119        the case of a simple NFS mount, the options that can be used are as
 120        specified in mount_nfs(1M), and location takes the form:
 121 
 122          host:pathname
 123 
 124 
 125 
 126 
 127        host is the name of the host from which to mount the file system, and
 128        pathname is the absolute pathname of the directory to mount.
 129 
 130 
 131        Options to other file systems are documented on the other mount_*
 132        reference manual pages, for example, mount_cachefs(1M).
 133 
 134    Replicated File Systems
 135        Multiple location fields can be specified for replicated NFS file
 136        systems, in which case automount and the kernel will each try to use
 137        that information to increase availability. If the read-only flag is set
 138        in the map entry, automountd mounts a list of locations that the kernel
 139        may use, sorted by several criteria. Only locations available at mount
 140        time will be mounted, and thus be available to the kernel. When a
 141        server does not respond, the kernel will switch to an alternate server.
 142        The sort ordering of automount is used to determine how the next server
 143        is chosen. If the read-only flag is not set, automount will mount the
 144        best single location, chosen by the same sort ordering, and new servers
 145        will only be chosen when an unmount has been possible, and a remount is
 146        done. Servers on the same local subnet are given the strongest
 147        preference, and servers on the local net are given the second strongest
 148        preference. Among servers equally far away, response times will
 149        determine the order if no weighting factors (see below) are used.
 150 
 151 
 152        If the list includes server locations using both the NFS Version 2


 302        the fstype option. The location field must contain information specific
 303        to the file system type. If the location field begins with a slash, a
 304        colon character must be prepended, for instance, to mount a CD file
 305        system:
 306 
 307          cdrom -fstype=hsfs,ro   :/dev/sr0
 308 
 309 
 310 
 311 
 312        or to perform an autofs mount:
 313 
 314          src -fstype=autofs    auto_src
 315 
 316 
 317 
 318 
 319        Use this procedure only if you are not using Volume Manager.
 320 
 321 
 322        Mounts using CacheFS are most useful when applied to an entire map as
 323        map defaults. The following entry in the master map describes cached
 324        home directory mounts. It assumes the default location of the cache
 325        directory, /cache.
 326 
 327          /home auto_home -fstype =cachefs,backfstype=nfs
 328 
 329 
 330 
 331 
 332        See the  NOTES section for information on option inheritance.
 333 
 334    Indirect Maps
 335        An indirect map allows you to specify mappings for the subdirectories
 336        you wish to mount under the directory indicated on the command line. In
 337        an indirect map, each key consists of a simple name that refers to one
 338        or more file systems that are to be mounted as needed.
 339 
 340    Direct Maps
 341        Entries in a direct map are associated directly with autofs mount
 342        points.  Each key is the full pathname of an autofs mount point. The
 343        direct map as a whole is not associated with any single directory.
 344 
 345 
 346        Direct maps are distinguished from indirect maps by the /- key. For
 347        example:
 348 
 349          # Master map for automounter
 350          #
 351          +auto_master


 469        /etc/auto_master
 470                               Master automount map.
 471 
 472 
 473        /etc/auto_home
 474                               Map to support automounted home directories.
 475 
 476 
 477        /etc/default/autofs
 478                               Supplies default values for parameters for
 479                               automount and automountd. See autofs(4).
 480 
 481 
 482        /etc/nsswitch.conf
 483                               Name service switch configuration file. See
 484                               nsswitch.conf(4).
 485 
 486 
 487 SEE ALSO
 488        isainfo(1), ls(1), svcs(1), uname(1), automountd(1M), mount(1M),
 489        mount_cachefs( 1M), mount_nfs(1M), svcadm(1M), autofs(4),
 490        attributes(5), nfssec(5), smf(5)
 491 
 492 
 493 
 494 NOTES
 495        autofs mount points must not be hierarchically related. automount does
 496        not allow an autofs mount point to be created within another autofs
 497        mount.
 498 
 499 
 500        Since each direct map entry results in a new autofs mount such maps
 501        should be kept short.
 502 
 503 
 504        Entries in both direct and indirect maps can be modified at any time.
 505        The new information is used when automountd next uses the map entry to
 506        do a mount.
 507 
 508 
 509        New entries added to a master map or direct map will not be useful
 510        until the automount command is run to install them as new autofs mount


 533 
 534 
 535        The Network Information Service (NIS) was formerly known as Sun Yellow
 536        Pages (YP). The functionality of the two remains the same.
 537 
 538 
 539        The automount service is managed by the service management facility,
 540        smf(5), under the service identifier:
 541 
 542          svc:/system/filesystem/autofs:default
 543 
 544 
 545 
 546 
 547        Administrative actions on this service, such as enabling, disabling, or
 548        requesting restart, can be performed using svcadm(1M). The service's
 549        status can be queried using the svcs(1) command.
 550 
 551 
 552 
 553                                 March 28, 2008                   AUTOMOUNT(1M)


  99 
 100 
 101        -v
 102                       Verbose mode. Notifies of autofs mounts, unmounts, or
 103                       other non-essential information.
 104 
 105 
 106 USAGE
 107    Map Entry Format
 108        A simple map entry (mapping) takes the form:
 109 
 110          key [ -mount-options ] location ...
 111 
 112 
 113 
 114 
 115        where key is the full pathname of the directory to mount when used in a
 116        direct map, or the simple name of a subdirectory in an indirect map.
 117        mount-options is a comma-separated list of mount options, and location
 118        specifies a file system from which the directory may be mounted.  In
 119        the case of a simple NFS mount, the options that can be used are
 120        specified in mount_nfs(1M), and location takes the form:
 121 
 122          host:pathname
 123 
 124 
 125 
 126 
 127        host is the name of the host from which to mount the file system, and
 128        pathname is the absolute pathname of the directory to mount.
 129 
 130 
 131        Options to other file systems are documented in the other mount_*
 132        reference manual pages.
 133 
 134    Replicated File Systems
 135        Multiple location fields can be specified for replicated NFS file
 136        systems, in which case automount and the kernel will each try to use
 137        that information to increase availability. If the read-only flag is set
 138        in the map entry, automountd mounts a list of locations that the kernel
 139        may use, sorted by several criteria. Only locations available at mount
 140        time will be mounted, and thus be available to the kernel. When a
 141        server does not respond, the kernel will switch to an alternate server.
 142        The sort ordering of automount is used to determine how the next server
 143        is chosen. If the read-only flag is not set, automount will mount the
 144        best single location, chosen by the same sort ordering, and new servers
 145        will only be chosen when an unmount has been possible, and a remount is
 146        done. Servers on the same local subnet are given the strongest
 147        preference, and servers on the local net are given the second strongest
 148        preference. Among servers equally far away, response times will
 149        determine the order if no weighting factors (see below) are used.
 150 
 151 
 152        If the list includes server locations using both the NFS Version 2


 302        the fstype option. The location field must contain information specific
 303        to the file system type. If the location field begins with a slash, a
 304        colon character must be prepended, for instance, to mount a CD file
 305        system:
 306 
 307          cdrom -fstype=hsfs,ro   :/dev/sr0
 308 
 309 
 310 
 311 
 312        or to perform an autofs mount:
 313 
 314          src -fstype=autofs    auto_src
 315 
 316 
 317 
 318 
 319        Use this procedure only if you are not using Volume Manager.
 320 
 321 










 322        See the  NOTES section for information on option inheritance.
 323 
 324    Indirect Maps
 325        An indirect map allows you to specify mappings for the subdirectories
 326        you wish to mount under the directory indicated on the command line. In
 327        an indirect map, each key consists of a simple name that refers to one
 328        or more file systems that are to be mounted as needed.
 329 
 330    Direct Maps
 331        Entries in a direct map are associated directly with autofs mount
 332        points.  Each key is the full pathname of an autofs mount point. The
 333        direct map as a whole is not associated with any single directory.
 334 
 335 
 336        Direct maps are distinguished from indirect maps by the /- key. For
 337        example:
 338 
 339          # Master map for automounter
 340          #
 341          +auto_master


 459        /etc/auto_master
 460                               Master automount map.
 461 
 462 
 463        /etc/auto_home
 464                               Map to support automounted home directories.
 465 
 466 
 467        /etc/default/autofs
 468                               Supplies default values for parameters for
 469                               automount and automountd. See autofs(4).
 470 
 471 
 472        /etc/nsswitch.conf
 473                               Name service switch configuration file. See
 474                               nsswitch.conf(4).
 475 
 476 
 477 SEE ALSO
 478        isainfo(1), ls(1), svcs(1), uname(1), automountd(1M), mount(1M),
 479        mount_nfs(1M), svcadm(1M), autofs(4), attributes(5), nfssec(5), smf(5)

 480 
 481 
 482 
 483 NOTES
 484        autofs mount points must not be hierarchically related. automount does
 485        not allow an autofs mount point to be created within another autofs
 486        mount.
 487 
 488 
 489        Since each direct map entry results in a new autofs mount such maps
 490        should be kept short.
 491 
 492 
 493        Entries in both direct and indirect maps can be modified at any time.
 494        The new information is used when automountd next uses the map entry to
 495        do a mount.
 496 
 497 
 498        New entries added to a master map or direct map will not be useful
 499        until the automount command is run to install them as new autofs mount


 522 
 523 
 524        The Network Information Service (NIS) was formerly known as Sun Yellow
 525        Pages (YP). The functionality of the two remains the same.
 526 
 527 
 528        The automount service is managed by the service management facility,
 529        smf(5), under the service identifier:
 530 
 531          svc:/system/filesystem/autofs:default
 532 
 533 
 534 
 535 
 536        Administrative actions on this service, such as enabling, disabling, or
 537        requesting restart, can be performed using svcadm(1M). The service's
 538        status can be queried using the svcs(1) command.
 539 
 540 
 541 
 542                                September 8, 2015                 AUTOMOUNT(1M)