Sponsored Content
Full Discussion: NFS vmount problem
Operating Systems AIX NFS vmount problem Post 302139721 by jess_t03 on Tuesday 9th of October 2007 01:14:36 AM
Old 10-09-2007
NFS vmount problem

AIX's NFS client sends requests on high port numbers by default, and
Linux rejects this as the security exposure it is. On AIX i'm use:

nfso -o nfs_use_reserved_ports=1

But how i can setup it in autorun? /etc/rc.local right way ?
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

NFS Problem !

Hi, I've mounted one of the file systems on another machine manually on /mnt located on my machine , after finishing my work i want to umount this /mnt , but all the time it says " nfs umount : /mnt : is busy " ,although it's not. so i tried to stop & start Nfs services manually (Incld :... (4 Replies)
Discussion started by: nikk
4 Replies

2. UNIX for Advanced & Expert Users

NFS Problem

For having shared file system i've been using nfs ,but regarding this i've some problem ,when i execute "df -ak" i can see the shared file system & i can also go there & list files ,but when i want to create anything in this area (Incld. file ,dir ....) i get permission denied. (i've shared related... (6 Replies)
Discussion started by: nikk
6 Replies

3. UNIX for Advanced & Expert Users

nfs problem help

I am having problem mounting my nfs mount on my sun solaris 8 through automount using the automaster file. this has been working fine until today, when my workstation tries to mount the nfs mount the following error is logged in /var/adm/message NFS lookup failed for server comserv: error 7... (2 Replies)
Discussion started by: hassan2
2 Replies

4. AIX

problem with NFS daemon?????

hi team we had a problem in mounting a network file system from source server to target server and we are not able to mount the file system and we checked all the configuration files and we execute the command in the source server lssrc -a | grep nfsd we found that 2 nfsd in that one is... (5 Replies)
Discussion started by: aixteam
5 Replies

5. AIX

nfs problem...

Got a prob.. I am trying to export a directory and mount it on to a server using NFS. My exporting goes fine as I am able to see the shares through "exportfs -v" But when I am trying to mount the directory on a the client.. I get an error.. "system call error number - 1" pls help.... ... (3 Replies)
Discussion started by: balaji_prk
3 Replies

6. Filesystems, Disks and Memory

FreeBSD NFS Problem

I am trying to setup 2 network shares that exist on a server. One of the shares is mounted but when i try to mount the second share I am greeted with: # mount srv:/data/music /data/music srv:/data/music: RPCPROG_NFS: RPC: Program not registered Server Info: name: srv #cat /etc/exports:... (0 Replies)
Discussion started by: ezekiel61
0 Replies

7. AIX

AIX5.3--vmount: Operation not permitted

Hi all, iam unable to mount exported directory hari on AIX 5.3, which was in RedHat Linux As4. Linux-server AIX -client I am facing errors of bash-3.00# mount -n linuxas4 /hari /hari mount: 1831-008 giving up on: linuxas4:/hari vmount: Operation not permitted. Pl any body... (1 Reply)
Discussion started by: haribabu
1 Replies

8. Solaris

Problem with NFS

Hi All, I have shared a directory from Linux machine which will be accessible from other linux servers without any problem. But when I try to access ( ie mount) on other Solaris machine, it is giving below error. #mount -F nfs IP of nfs server:/share /localmountpoint nfs mount : mount:... (1 Reply)
Discussion started by: naw_deepak
1 Replies

9. AIX

Problem with NFS

Hello everyone I need to share a file system with two Aix boxes, the version is 5.3 tl9. I create the nfs and I can see the files from both servers, but the problem with one of them is that I can write on the file or If I create a new one I canīt. On the server that I create the... (5 Replies)
Discussion started by: lo-lp-kl
5 Replies

10. SCO

Problem with nfs exports between 5.0.5 and 5.0.7

Hello everyone! I have two systems: an old SCO 5.0.5 Openserver (here's the uname -a output): /# uname -a SCO_SV munixela 3.2 5.0.5 i386 And a SCO 5.0.7 OpenServer (uname -a output): /# uname -a SCO_SV catedral 3.2 5.0.7 i386 I exported a Filesystem from the 5.0.7 machine, using the... (13 Replies)
Discussion started by: superchivo
13 Replies
rpc.statd(8)						      System Manager's Manual						      rpc.statd(8)

NAME
rpc.statd - NSM status monitor SYNOPSIS
rpc.statd [-FNL] [-d] [-?] [-n name ] [-o port ] [-p port ] [-H prog ] [-V] DESCRIPTION
The rpc.statd server implements the NSM (Network Status Monitor) RPC protocol. This service is somewhat misnamed, since it doesn't actu- ally provide active monitoring as one might suspect; instead, NSM implements a reboot notification service. It is used by the NFS file locking service, rpc.lockd, to implement lock recovery when the NFS server machine crashes and reboots. Operation For each NFS client or server machine to be monitored, rpc.statd creates a file in /var/lib/nfs/sm. When starting, it normally runs sm- notify to iterate through these files and notify the peer rpc.statd on those machines. OPTIONS
-F By default, rpc.statd forks and puts itself in the background when started. The -F argument tells it to remain in the foreground. This option is mainly for debugging purposes. -d By default, rpc.statd sends logging messages via syslog(3) to system log. The -d argument forces it to log verbose output to stderr instead. This option is mainly for debugging purposes, and may only be used in conjunction with the -F parameter. -n, --name name specify a name for rpc.statd to use as the local hostname. By default, rpc.statd will call gethostname(2) to get the local hostname. Specifying a local hostname may be useful for machines with more than one interfaces. -o, --outgoing-port port specify a port for rpc.statd to send outgoing status requests from. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -p, --port port specify a port for rpc.statd to listen on. By default, rpc.statd will ask portmap(8) to assign it a port number. As of this writ- ing, there is not a standard port number that portmap always or usually assigns. Specifying a port may be useful when implementing a firewall. -P, --state-directory-path directory specify a directory in which to place statd state information. If this option is not specified the default of /var/lib/nfs is used. -N Causes statd to run in the notify-only mode. When started in this mode, the statd program will check its state directory, send noti- fications to any monitored nodes, and exit once the notifications have been sent. This mode is used to enable Highly Available NFS implementations (i.e. HA-NFS). This mode is deprecated - sm-notify should be used directly instead. -L, --no-notify Inhibits the running of sm-notify. If sm-notify is run by some other script at boot time, there is no need for statd to start sm- notify itself. This can be appropriate if starting of statd needs to be delayed until it is actually need. In such cases sm-notify should still be run at boot time. -H, --ha-callout prog Specify a high availability callout program, which will receive callouts for all client monitor and unmonitor requests. This allows rpc.statd to be used in a High Availability NFS (HA-NFS) environment. The program will be run with 3 arguments: The first is either add-client or del-client depending on the reason for the callout. The second will be the name of the client. The third will be the name of the server as known to the client. -? Causes rpc.statd to print out command-line help and exit. -V Causes rpc.statd to print out version information and exit. TCP_WRAPPERS SUPPORT This rpc.statd version is protected by the tcp_wrapper library. You have to give the clients access to rpc.statd 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: statd: .bar.com You have to use the daemon name statd 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. SIGNALS
SIGUSR1 causes rpc.statd to re-read the notify list from disk and send notifications to clients. This can be used in High Availability NFS (HA-NFS) environments to notify clients to reacquire file locks upon takeover of an NFS export from another server. FILES
/var/lib/nfs/state /var/lib/nfs/sm/* /var/lib/nfs/sm.bak/* SEE ALSO
rpc.nfsd(8), portmap(8) AUTHORS
Jeff Uphoff <juphoff@users.sourceforge.net> Olaf Kirch <okir@monad.swb.de> H.J. Lu <hjl@gnu.org> Lon Hohberger <hohberger@missioncriticallinux.com> Paul Clements <paul.clements@steeleye.com> 31 Aug 2004 rpc.statd(8)
All times are GMT -4. The time now is 11:00 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy