Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Cyber Angels

 Create an AccountHome | Submit News | Your Account  

Tutorial Menu
Linux Tutorial Home
Table of Contents

· Introduction to Operating Systems
· Linux Basics
· Working with the System
· Shells and Utilities
· Editing Files
· Basic Administration
· The Operating System
· The X Windowing System
· The Computer Itself
· Networking
· System Monitoring
· Solving Problems
· Security
· Installing and Upgrading
· Linux and Windows

Glossary
MoreInfo
Man Pages
Linux Topics
Test Your Knowledge

Site Menu
Site Map
FAQ
Copyright Info
Terms of Use
Privacy Info
Disclaimer
WorkBoard
Thanks
Donations
Advertising
Masthead / Impressum
Your Account

Communication
Feedback
Forums
Private Messages
Surveys

Features
HOWTOs
News Archive
Submit News
Topics
User Articles
Web Links

Google
Google


The Web
linux-tutorial.info

Who's Online
There are currently, 169 guest(s) and 0 member(s) that are online.

You are an Anonymous user. You can register for free by clicking here

  

autofs



DESCRIPTION

       The  automounter maps are files or NIS maps referred to by
       the master map of the  automounter  (see  auto.master(5)).
       The  automounter  maps describe how file systems below the
       mountpoint of the map (given in the auto.master file)  are
       to  be  mounted.   This  describes  the sun map format; if
       another map format is specified (e.g. hesiod), this  docu­
       mentation does not apply.

       Maps  can  be  changed  on the fly and the automouter will
       recognize those changes on the next operation it  performs
       on that map.  This is not true for the auto.master map!


FORMAT

       This  is  a  description  of  the text file format.  Other
       methods of specifying these files may  exist.   All  empty
       lines  or  lines  beginning  with # are ignored. The basic
       format of one line in such maps is:

       key [-options] location

   key
       is the part of the pathname between the mountpoint and the
       path  into  the filesystem mounted.  Usually you can think
       about the key as a subdirectory name below the mountpoint.

   options
       Options  are  optional.   Options can also be given in the
       auto.master file in which case both values are  cumulative
       (this is a difference from SunOS).  The options are a list
       of comma separated options as customary for  the  mount(8)
       command.  There is a special option -fstype= used to spec­
       ify a filesystem type if the  filesystem  is  not  of  the
       default  NFS  type.  This option is processed by the auto­
       mounter and not by the mount command.

   location
       The location specifies from where the file system is to be
       mounted.  In the most cases this will be an NFS volume and
       the usual notation host:pathname is used to  indicate  the
       remote filesystem and path to be mounted.  If the filesys­
       tem to be mounted begins with a  /  (such  as  local  /dev
       entries  or  smbfs  shares) a : needs to be prefixed (e.g.
       :/dev/sda1).


EXAMPLE

         kernel    -ro,soft,intr       ftp.kernel.org:/pub/linux
         boot      -fstype=ext2        :/dev/hda1
         windoze   -fstype=smbfs       ://windoze/c

       the key field that matched the line (which  probably  only
       makes sense together with a wildcard key).

   Wildcard Key
       A * in the key field matches all keys.  An example for the
       usefulness is the following entry:

         *         &:/home/&

       This will enable you to access all the home  directory  of
       local  hosts  using  the  path /mountpoint/hostname/local-
       path.

   Variable Substitution
       The following special variables will be substituted in the
       key  and location fields of an automounter map if prefixed
       with $ as customary from shell scripts (Curly  braces  can
       be used to separate the fieldname):

         ARCH           Architecture (uname -m)
         CPU            Processor Type
         HOST           Hostname (uname -n)
         OSNAME         Operating System (uname -s)
         OSREL          Release of OS (uname -r)
         OSVERS         Version of OS (uname -v)

       Additional   entries  can  be  defined  with  the  -Dvari­
       able=Value option to automount(8).

   Executable Maps
       A map can be marked as executable.  The init  script  that
       parses the auto.master map will pass this as a program map
       to the automounter.  A program map will  be  called  as  a
       script  with  the key as an argument.  The script needs to
       return one line of a map or no output at all  if  the  key
       cannot be matched.

       To  do this the automount(8) daemon has to be started with
       the program type insted of the file type.  This is  imple­
       mented in the initialization script.

       A  executable  map can return an errorcode to indicate the
       failure in addition to no output at all.  All output  sent
       to stderr is logged into the system logs.


UNSUPPORTED

       The  automounter  does  not  support  direct maps or mount
       trees (more than one filesystem to be mounted under a spe­
       cific automount point), and handles SunOS-style replicated
       filesystems only to the extent that mount(8) does.


SEE ALSO


  




Login
Nickname

Password

Security Code
Security Code
Type Security Code


Don't have an account yet? You can create one. As a registered user you have some advantages like theme manager, comments configuration and post comments with your name.

Help if you can!


Amazon Wish List

Did You Know?
You can get all the latest Site and Linux news by checking out our news page.


Friends



Tell a Friend About Us

Bookmark and Share



Web site powered by PHP-Nuke

Is this information useful? At the very least you can help by spreading the word to your favorite newsgroups, mailing lists and forums.
All logos and trademarks in this site are property of their respective owner. The comments are property of their posters. Articles are the property of their respective owners. Unless otherwise stated in the body of the article, article content (C) 1994-2013 by James Mohr. All rights reserved. The stylized page/paper, as well as the terms "The Linux Tutorial", "The Linux Server Tutorial", "The Linux Knowledge Base and Tutorial" and "The place where you learn Linux" are service marks of James Mohr. All rights reserved.
The Linux Knowledge Base and Tutorial may contain links to sites on the Internet, which are owned and operated by third parties. The Linux Tutorial is not responsible for the content of any such third-party site. By viewing/utilizing this web site, you have agreed to our disclaimer, terms of use and privacy policy. Use of automated download software ("harvesters") such as wget, httrack, etc. causes the site to quickly exceed its bandwidth limitation and are therefore expressly prohibited. For more details on this, take a look here

PHP-Nuke Copyright © 2004 by Francisco Burzi. This is free software, and you may redistribute it under the GPL. PHP-Nuke comes with absolutely no warranty, for details, see the license.
Page Generation: 0.04 Seconds