First a (minor) appeal: for quotes please use "QUOTE"-tags, not "CODE"-tags. The resulting formatting is different and it is easier that way to keep track of various parts of a posting. Thank you for your consideration.
Quote:
Originally Posted by Phat
I use the method you mentioned, but use the parameter s, not g
The difference is that stopsrc -s only stops a single service (in this case nfsd) whereas stopsrc -g stops a group of services altogether. If you do a lssrc you will see the various groups the services belong to mentioned. You can use this group name to manage whole groups instead of single services. The same goes for startsrc and refresh.
NFS is not only nfsd but also portmapper, biod and statd (and maybe something else, i have no AIX system at hand and am quoting from failing memory). With the -g option you can manage the whole affected group (which is "nfs", not "nfsd"!).
Quote:
Originally Posted by Phat
Thank you for your mount command. With mount command I found this:
LOL, i know the feeling. Have you ever considered using a sledgehammer on the persons private parts? This, i think, is called "best practice" as it not only drives home the message but also prevents procreation of such people. ;-))
Hi
i am using HPUX11.00 and i am facing a starnge problem
after some time when i log on a message is coimng
NFS server not responding still trying....and it keps on coming there is no other way but to log out..form the server and start once again...
there is no file system exported or NFS... (3 Replies)
I'm in panic mode. This isn't a production server, however, is very vital to office.
Sun V240 with Solaris 9, stopped accepting ftp sessions. When I tried to remote into box, it didn't respond. I have tried rebooting to boot in single user mode, no luck. I can see that it is ON but I can't get it... (3 Replies)
At times I have unknown applications that hang for long periods of time over and over again after a network glitch. These are sometimes nfs4 but usually nfs3 clients and are always solaris10 systems.
nfs: NFS server hostname not responding still trying
nfs: NFS server hostname ok
nfs: NFS... (1 Reply)
Hello,
I have a centos as nfs server, its name is centos_A.
After I finish the setup of the nfs server, the other linux can access this nfs server immediately via /net/centos_A/*
But,
My solaris 9 can not access /net/centos_A/* immediately. I have to leave /net/centos_A, and wait for about... (1 Reply)
Hi gurus,
OS = SunOS 5.8
Not sure whether to post this in the scripting one or to advance and experts. Am posting on both since there is two things that am wanting to achieve.
Am currerntly having NFS server errors below. At this stage, I am not sure whether I am having a SAN storage issue... (2 Replies)
Greetings!
I'm testing a failover solution for NFSv4 on RHEL6 with latest updates.
My script umounts (umount -lf /share) the faulty NFS share if it sees that's hanging on the client (the NFS daemon is down on the NFS server) and it mounts the share from another healthy NFS server.
Sometimes... (4 Replies)
Server is accessible only via IPMI. SSH and web control panel is timeout. Takes several hours. Server dont have high load or suspicious processes.
I checked /etc/hosts.deny and restarted ssh, but nothing :( (0 Replies)
Hi 2 ALL,
try to run NFS Server in AIX 7.1 :
1. Step by step on NFS Server node
mkdir /tmp/test
chgrp staff /tmp/test
chmod 775 /tmp/test-- create export directory (fs)
mknfsexp -d /tmp/test -t ro
exportfs -va
show mount -e
:/# exportfs -av
exports: 1831-187 re-exported /tmp/test... (4 Replies)
Discussion started by: penchev
4 Replies
LEARN ABOUT DEBIAN
nfsd
rpc.nfsd(8) System Manager's Manual rpc.nfsd(8)NAME
rpc.nfsd - NFS server process
SYNOPSIS
/usr/sbin/rpc.nfsd [options] nproc
DESCRIPTION
The rpc.nfsd program implements the user level part of the NFS service. The main functionality is handled by the nfsd kernel module. The
user space program merely specifies what sort of sockets the kernel service should listen on, what NFS versions it should support, and how
many kernel threads it should use.
The rpc.mountd server provides an ancillary service needed to satisfy mount requests by NFS clients.
OPTIONS -d or --debug
enable logging of debugging messages
-H or --host hostname
specify a particular hostname (or address) that NFS requests will be accepted on. By default, rpc.nfsd will accept NFS requests on
all known network addresses. Note that lockd (which performs file locking services for NFS) may still accept request on all known
network addresses. This may change in future releases of the Linux Kernel.
-p or --port port
specify a different port to listen on for NFS requests. By default, rpc.nfsd will listen on port 2049.
-N or --no-nfs-version vers
This option can be used to request that rpc.nfsd does not offer certain versions of NFS. The current version of rpc.nfsd can support
both NFS version 2,3 and the newer version 4.
-s or --syslog
By default, rpc.nfsd logs error messages (and debug messages, if enabled) to stderr. This option makes rpc.nfsd log these messages
to syslog instead. Note that errors encountered during option processing will still be logged to stderr regardless of this option.
-T or --no-tcp
Disable rpc.nfsd from accepting TCP connections from clients.
-U or --no-udp
Disable rpc.nfsd from accepting UDP connections from clients.
nproc specify the number of NFS server threads. By default, just one thread is started. However, for optimum performance several threads
should be used. The actual figure depends on the number of and the work load created by the NFS clients, but a useful starting point
is 8 threads. Effects of modifying that number can be checked using the nfsstat(8) program.
Note that if the NFS server is already running, then the options for specifying host, port, and protocol will be ignored. The number of
processes given will be the only option considered, and the number of active nfsd processes will be increased or decreased to match this
number. In particular rpc.nfsd 0 will stop all threads and thus close any open connections.
NOTES
If the program is built with TI-RPC support, it will enable any protocol and address family combinations that are marked visible in the
netconfig database.
SEE ALSO nfsd(7), rpc.mountd(8), exports(5), exportfs(8), rpc.rquotad(8), nfsstat(8), netconfig(5).
AUTHOR
Olaf Kirch, Bill Hawes, H. J. Lu, G. Allan Morris III, and a host of others.
7 Aug 2006 rpc.nfsd(8)