03-20-2010
You are
exporting to hosts on the 192.168.1.0/24, should that have -network before it?
What is the IP address of your NFS client?
10 More Discussions You Might Find Interesting
1. SCO
Hi,
We are testing SCO6 for an upgrade.
We currently have a SCO5.0.4 system that mounts
a remote directory on a Windows 2000 server.
The windows server has 'services for unix' installed
to enable the required directory to be mounted on the SCO system.
On SCO we run '/etc/mount -v -f NFS... (2 Replies)
Discussion started by: sidnagra
2 Replies
2. Solaris
While mounting nfs file system I get the following error .
# mount -F nfs jewelex:/back2 /oback2
nfs mount: jewelex:/back2: Permission denied
Following is the permission for oback2
drwxr-xr-x 2 root other 512 Apr 9 18:39 oback2
Directory permission on jewelex server is ... (4 Replies)
Discussion started by: Hitesh Shah
4 Replies
3. Solaris
On my Solaris 10 server, I want to share out the directory /export/home/data, so in the /etc/dfs/dfstab file, I have this line:
share -F nfs -o rw /export/home/data
In the /etc/hosts.equiv file, I have this:
+
When I do a "ps -ef" command, I see that the "nfsd' daemon is started.
... (2 Replies)
Discussion started by: serendipity1276
2 Replies
4. UNIX for Dummies Questions & Answers
For my kickstart install I use an NFS share on another machine in order to install the packages. For the most part, all configuration required after each time I reimage is set up in the kickstart file, but this one portion is giving me issues. I'm trying to mount an NFS share in the kickstart post... (0 Replies)
Discussion started by: Colton
0 Replies
5. Solaris
Hi all,
I had share the server Gemini /u10 to the server Centaurus.
/etc/dfs/dfstab
share -F nfs -o root=centaurus /u10
My problem is:
in the server Gemini the the owner for /U10 is oracle:dba
but when in the server Centaurus, I am not able to change the owner become oracle:dba, it show... (8 Replies)
Discussion started by: SmartAntz
8 Replies
6. Web Development
Hi,
I want to mount an NFS Shared folder on Windows XP to vxWorks.
There doesnt seem to be a problem with the sharing.
Now, when i try to mount the directory onto vxWorks (it runs on a Tumbleweed card), using a mount script (.sh), the following is the print i see on Tera Term:
hostAdd... (0 Replies)
Discussion started by: chinmayzen
0 Replies
7. UNIX for Advanced & Expert Users
Hi Guru's,
I am unable to mount NFS share on unix system (DG/UX) which is nfs client.
Error:
mount: /nfsshare: Invalid argument
mount: giving up on:
/mountpoint
i tried following command
mount -t nfs remotehost:/nfsshare /mountpoint
Error: (5 Replies)
Discussion started by: Justin John
5 Replies
8. Red Hat
All,
I re-wrote our scripts to speed-up the compiling time, original time is about 1hrs. now dispatch the sub task to different servers through SSH. Now my question is that:
If dispatch these tasks into the current server, there is no errors during compiling process.
If dispatch these tasks... (0 Replies)
Discussion started by: fduan001
0 Replies
9. Solaris
Hi all, new here.
I'm attempting to mount an NFS share I've created on a 2012r2 esx VM on my solaris 10 vm, I'm using the following command:
mount 2012box:/sharename /mnt
and I get the following result:
nfs mount: mount: /mnt: Operation not supported
Both vms can ping one... (3 Replies)
Discussion started by: Meshuggener
3 Replies
10. Shell Programming and Scripting
I need a help of good people with effective bash script to mount nfs shared,
By the way I did the searches, since i haven't found that someone wrote a script like this in the past, I'm sure it will serve more people.
The scenario as follow:
An NFS Client with Daily CRON , running bash script... (4 Replies)
Discussion started by: Brian.t
4 Replies
LEARN ABOUT REDHAT
mountd
rpc.mountd(8) System Manager's Manual rpc.mountd(8)
NAME
rpc.mountd - NFS mount daemon
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
daemon.
Alternatively, you can export individual directories temporarily 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 proce-
dure. 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 for kind.
-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.
-h or --help
Display usage message.
-o num or --descriptors num
Set the limit of the number of open file descriptors to num. The default is 256.
-N or --no-nfs-version
This option can be used to request that rpc.mountd do not offer certain versions of NFS. The current version of rpc.mountd can sup-
port both NFS version 2 and the newer version 3. If the NFS kernel module was compiled without support for NFSv3, rpc.mountd 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 following 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)