I am facing some issues during boot process of rhel 6.2
It takes too long time (~10 min) for the node to come up...
The boot process stuck while it trying to start NFS and does not continue until timeout.
Hi,
I have a program that check the IP address and automatic update it to the DNS server. I would like to run this program when the computer bootup after pppd get a connection. How do I add it to the init file. Does any one have any information of how to do it.
I run a Linux Mandrake as a... (1 Reply)
ok i am pretty new i am thinking this maybe a dns situatioan i dunno....
i am trying to start nfs server i get the followin error:
mountd svc_tli create could not bind to requested address: address mismatch
svc_create: svc_tli_create failed
/usr/lib/nfs/nfsd : tli_bind to wrong address... (14 Replies)
Hi,
Can someone help me on this?
I'm not able to enable a well working mounting process for NFS filesystems on boot time.
On the server side (AIX 5.2) everything seems to be OK and correctly exported, seeing other clients (AIX 5.2) are able to mount normally on boot time.
On a client in... (5 Replies)
Hi all,
I'm doing automation task for my team and I just started to learn unix scripting so please shed some light on how to do this:
1) I have 2 sets of datafiles - datafile A and B. These datafiles must be loaded subsequently and cannot be loaded concurrently.
2) So I loaded datafile A... (10 Replies)
When I get start program at boot
I read which run level
/sbin/rcx.d runlevel=0.....x
only read directory which directory name has UpperCase 'S'
is not enough
someone says that I need to reference another file
which file I need to reference
1)/etc/rc.config.d/all file which parameter... (4 Replies)
What I need to learn is how to use a script that launches background processes, and then kills those processes as needed.
The script successfully launches the script. But how do I check to see if the job exists before I kill it?
I know my problem is mostly failure to understand parameter... (4 Replies)
hi guys
I have a server suse 11 two IP different segments
one IP is point to point to NFS Storage.
Administration IP: 10.7.10.100
NFS-Storage IP: 192.168.10.50
weird thing is I defined the NFS I can mount them using mount -a but when I reboot the server the NFS mount points are not there... (11 Replies)
Hello,
I have a newly kickstarted RHEL 6.4 server that I'm trying to set-up as a kickstart server. I have done this before on other machines, but I am encountering some strange behaviour in this one.
# service nfs status
rpc.svcgssd is stopped
rpc.mountd is stopped
nfsd is stopped... (0 Replies)
Discussion started by: Chopstyx
0 Replies
LEARN ABOUT CENTOS
rpc.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. This option can be used multiple time to listen to more
than one interface.
-p or --port port
specify a different port to listen on for NFS requests. By default, rpc.nfsd will listen on port 2049.
-r or --rdma
specify that NFS requests on the standard RDMA port ("nfsrdma", port 20049) should be honored.
--rdma=port
Listen for RDMA requests on an alternate port - may be a number or a name listed in /etc/services.
-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
NFS versions 2,3,4 and the newer version 4.1.
-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.
-V or --nfs-version vers
This option can be used to request that rpc.nfsd offer certain versions of NFS. The current version of rpc.nfsd can support NFS ver-
sions 2,3,4 and the newer version 4.1.
-L or --lease-time seconds
Set the lease-time used for NFSv4. This corresponds to how often clients need to confirm their state with the server. Valid range
is from 10 to 3600 seconds.
-G or --grace-time seconds
Set the grace-time used for NFSv4 and NLM (for NFSv2 and NFSv3). New file open requests (NFSv4) and new file locks (NLM) will not
be allowed until after this time has passed to allow clients to recover state.
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 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.
20 Feb 2014 rpc.nfsd(8)