Welcome to Linux Knowledge Base and Tutorial
"The place where you learn linux"
Let The Music Play: Join EFF Today

 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, 56 guest(s) and 0 member(s) that are online.

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

  

mountd



SYNOPSIS

       /usr/sbin/rpc.mountd [options]


DESCRIPTION

       The  rpc.mountd program implements the NFS mount protocol.
       When receiving a MOUNT request  from  an  NFS  client,  it
       checks  the request against the list of currently exported
       file systems. If the client is permitted to mount the file
       system,  rpc.mountd  obtains  a  file handle for requested
       directory and returns it to the client.

   Exporting NFS File Systems
       Making file systems available to  NFS  clients  is  called
       exporting.

       Usually,  a  file  system  and the hosts it should be made
       available to are listed  in  the  /etc/exports  file,  and
       invoking  exportfs  -a  whenever the system is booted. The
       exportfs(8) command makes export information available  to
       both  the kernel NFS server module and the rpc.mountd dae­
       mon.

       Alternatively, you can export individual directories  tem­
       porarily using exportfs's host:/directory syntax.

   The rmtab File
       For  every  mount  request  received  from  an NFS client,
       rpc.mountd adds an entry to the  /var/lib/nfs/rmtab  file.
       When  receiving an unmount request, that entry is removed.
       user level part of the NFS service.

       However, this file is mostly ornamental. One,  the  client
       can  continue  to  use  the file handle even after calling
       rpc.mountd 's UMOUNT  procedure.  And  two,  if  a  client
       reboots  without notifying rpc.mountd , a stale entry will
       remain in rmtab.


OPTIONS

       -d kind  or  --debug kind
              Turn on debugging.  Valid  kinds  are:  all,  auth,
              call, general and parse.

       -F  or  --foreground
              Run in foreground (do not daemonize)

       -f  or  --exports-file
              This option specifies the exports file, listing the
              clients that this server is prepared to  serve  and
              parameters   to  apply  to  each  such  mount  (see
              exports(5)).  By  default,  export  information  is
              read from /etc/exports.

              must be invoked with the option --no-nfs-version  3
              .

       -n  or  --no-tcp
              Don't advertise TCP for mount.

       -P     Ignored (compatibility with unfsd??).

       -p  or  --port num
              Force rpc.mountd to bind to the specified port num,
              instead of using the random port number assigned by
              the portmapper.

       -V  or  --nfs-version
              This  option can be used to request that rpc.mountd
              offer certain versions of NFS. The current  version
              of  rpc.mountd  can  support both NFS version 2 and
              the newer version 3.

       -v  or  --version
              Print the version of rpc.mountd and exit.


TCP_WRAPPERS SUPPORT

       This rpc.mountd version is protected  by  the  tcp_wrapper
       library. You have to give the clients access to rpc.mountd
       if they should be allowed to use  it.  To  allow  connects
       from clients of the .bar.com domain you could use the fol­
       lowing line in /etc/hosts.allow:

       mountd: .bar.com

       You have to use the daemon name mountd for the daemon name
       (even if the binary has a different name).

       For  further information please have a look at the tcpd(8)
       and hosts_access(5) manual pages.


SEE ALSO

       rpc.nfsd(8), exportfs(8), exports(5), rpc.rquotad(8).


FILES

       /etc/exports, /var/lib/nfs/xtab.


AUTHOR

       Olaf Kirch, H. J. Lu, G. Allan Morris III, and a  host  of
       others.

                           25 Aug 2000              rpc.mountd(8)
  




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?
The Linux Tutorial can use your help.


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.09 Seconds