10 More Discussions You Might Find Interesting
1. Slackware
Hi.
Using debian 8.0 on a raspberryPI SERVER, accessing nfs from another raspberry gives quick reply.
But from a slackware 14.1 SERVER on a Celeron 2Ghz dual core, is painfully slow and i cannot figure out why.
Can anyone guide me? (2 Replies)
Discussion started by: dimples
2 Replies
2. HP-UX
Hi,
I see following 'nfsd' command is using more CPU. Could someone please comment on it's pros and cons of it?
CPU TTY PID USERNAME PRI NI SIZE RES STATE TIME %WCPU %CPU COMMAND
5 ? 16890 root 152 20 34696K 12036K run 57166:48 856.13 854.64 nfsd
OS -- HP-UX
One... (4 Replies)
Discussion started by: Maddy123
4 Replies
3. AIX
Hello,
what is the relation between portmap and nfsd and how communication between them looks like. Does the nfsclient contact with the portmap or nfsd first.
Many thanks in advance for helping me to understand this :)
BR,
p (3 Replies)
Discussion started by: pitmod
3 Replies
4. UNIX for Advanced & Expert Users
Dear Friends,
we are using HP-UX B.11.31 U ia64 HP-UX server. Can you check bellow the top command output whether can point out any abnormality. Becoz i suspect something wrong there,
Load averages: 2.40, 2.73, 2.99
711 processes: 287 sleeping, 424 running
Cpu states:
CPU LOAD USER ... (4 Replies)
Discussion started by: Davinzy
4 Replies
5. BSD
hello ,
I wondered if anyone could assist me in writing a simple packet filter firewall on my OpenBSD v4.5.
All I intend doing is to have two firewalling machine on a separate network :
192.168.1.1
ext_if = xl0 (dhcp) // Internet interface
int_if=xl1 // Internatl interface
... (0 Replies)
Discussion started by: mattjam
0 Replies
6. BSD
I am an eight year Linux user and after getting into an argument with someone about OpenBSD overiding my theory that OS security is 50% OS and 50% admin skill, I decided to try OpenBSD for myself. I've tried BSDs before and haven't been able to get into them for day to dy use, but I am going to... (7 Replies)
Discussion started by: deckard
7 Replies
7. UNIX for Dummies Questions & Answers
hi guys
I installed NFS server and everything started out fine but I don't have /proc/fs/nfsd entry and so I can't mount nfsd. Therefore I can't start my nfs service.
Why don't I have /proc/fs/nfsd? How do I create that?
Thanks (1 Reply)
Discussion started by: alirezan
1 Replies
8. Solaris
Hi
Inexplicably, nfsd no longer starts automatically on our Sun boxes running Solaris 9, so that 'automount' no longer functions automatically. The problem first manifested itself when we could not access files on any of the nfs automounted directories in our LAN after one of the servers (say... (19 Replies)
Discussion started by: dcshungu
19 Replies
9. BSD
hi
OK. I don't know exactly what I did to system!
The system is OpenBSD 3.5.
It is 200MMX, 16MB ram 1.2 + 2.4 GB HDD. The system was running well. But a few days ago I try to unpack a big tar.gz file and the system uses most the cpu and ram for this. While the system unpacking the file I try to... (4 Replies)
Discussion started by: fnoyan
4 Replies
10. UNIX for Dummies Questions & Answers
Please help. I have downloaded the openbsd 2.9 snapshot from ftp.openbsd.org. the following files were downloaded from the snapshot dir. ( the whole dir. was downloaded ) base29,bsd,bsd.rd,cdrom29.fs,cksum,comp29,etc29,all three floppy images,game29,index,install.ata,install.chs... (11 Replies)
Discussion started by: Blunt_Killer
11 Replies
nfsd(1M) nfsd(1M)
NAME
nfsd - NFS daemon
SYNOPSIS
/usr/lib/nfs/nfsd [-a] [-c #_conn] [-l listen_backlog] [-p protocol] [-t device] [nservers]
nfsd is the daemon that handles client file system requests. Only users with {PRIV_SYS_NFS} and sufficient privileges to write to /var/run
can run this daemon.
The nfsd daemon is automatically invoked using share(1M) with the -a option.
By default, nfsd starts over the TCP and UDP transports for versions 2 and 3. By default, it starts over the TCP for version 4. You can
change this with the -p option.
A previously invoked nfsd daemon started with or without options must be stopped before invoking another nfsd command.
Administrators wanting to change startup parameters for nfsd should, as root, make changes in the /etc/default/nfs file. See nfs(4).
The following options are supported:
-a Start a NFS daemon over all available connectionless and connection-oriented transports, including UDP and TCP. Equivalent
of setting the NFSD_PROTOCOL parameter to ALL in the nfs file.
-c #_conn This sets the maximum number of connections allowed to the NFS server over connection-oriented transports. By default, the
number of connections is unlimited. Equivalent of the NFSD_MAX_CONNECTIONS parameter in the nfs file.
-l Set connection queue length for the NFS TCP over a connection-oriented transport. The default value is 32 entries. Equiva-
lent of the NFSD_LISTEN_BACKLOG parameter in the nfs file.
-p protocol Start a NFS daemon over the specified protocol. Equivalent of the NFSD_PROTOCOL parameter in the nfs file.
-t device Start a NFS daemon for the transport specified by the given device. Equivalent of the NFSD_DEVICE parameter in the nfs
file.
The following operands are supported:
nservers This sets the maximum number of concurrent NFS requests that the server can handle. This concurrency is achieved by up to
nservers threads created as needed in the kernel. nservers should be based on the load expected on this server. 16 is the
usual number of nservers. If nservers is not specified, the maximum number of concurrent NFS requests will default to 1.
Equivalent of the NFSD_SERVERS parameter in the nfs file.
USAGE
If the NFS_PORTMON variable is set in /etc/system, then clients are required to use privileged ports (ports < IPPORT_RESERVED) to get NFS
services. This variable is equal to zero by default. This variable has been moved from the "nfs" module to the "nfssrv" module. To set the
variable, edit the /etc/system file and add this entry:
set nfssrv:nfs_portmon = 1
0 Daemon started successfully.
1 Daemon failed to start.
.nfsXXX Client machine pointer to an open-but-unlinked file.
/etc/default/nfs Contains startup parameters for nfsd.
/etc/system System configuration information file.
/var/nfs/v4_state Directories used by the server to manage client state information. These directories should not be removed.
/var/nfs/v4_oldstate
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWnfssu |
+-----------------------------+-----------------------------+
ps(1), svcs(1), mountd(1M), share(1M), svcadm(1M), nfs(4), sharetab(4), system(4), attributes(5), smf(5)
Manually starting and restarting nfsd is not recommended. If it is necessary to do so, use svcadm to enable or disable the nfs service
(svc:/network/nfs/server). If it is disabled, it will be enabled by share_nfs(1M), unless its application/auto_enable property is set to
false. See the , and svcadm(1M) for more information.
The nfsd service is managed by the service management facility, smf(5), under the service identifier:
svc:/network/nfs/server
Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). The ser-
vice's status can be queried using the svcs(1) command.
If nfsd is killed with SIGTERM, it will not be restarted by the service management facility. Instead, nfsd can be restarted by other sig-
nals, such as SIGINT.
27 Apr 2005 nfsd(1M)