nfssvc(2) System Calls Manual nfssvc(2)NAME
nfssvc - Creates a remote NFS server
SYNOPSIS
nfssvc(
unsigned long udp_so,
unsigned long udp_num,
unsigned long tcp_so,
unsigned long tcp_num);
PARAMETERS
Specifies a UDP socket bound to port 2049. Specifies the number of UDP NFS server threads to start (in the low 32 bits) and 950410 (in the
high 32 bits). Specifies a TCP socket bound to port 2049 after a call to listen(2). Specifies the number of TCP NFS server threads to
start.
DESCRIPTION
The use of the nfssvc() function is not supported in customer applications, and the interface is subject to change without notice. It is
intended for use solely by nfsd(8).
The nfssvc() function starts NFS server kernel threads and provides TCP connection support. If the value of the upper 32 bits of udp_num
is not 950410, TCP threads are not started.
RETURN VALUES
The nfssvc() function has no successful return. In fact, it frees the text and data segments associated with the calling program so there
is nothing to return to. When interrupted by a KILL signal, the server threads are terminated and the process exits. If nfssvc() encoun-
ters errors, -1 is returned and errno is set to indicate the error.
ERRORS
If the nfssvc() function fails, errno may be set to one of the following values: Another process is executing nfssvc. An invalid file
descriptor has been passed to the nfssvc() function. More than 128 server and netisr threads were requested. The caller is not the supe-
ruser.
RELATED INFORMATION
Functions: async_daemon(2)
Commands: nfsd(8) delim off
nfssvc(2)
Check Out this Related Man Page
async_daemon(2) System Calls Manual async_daemon(2)NAME
async_daemon - Creates a local NFS asynchronous I/O server
SYNOPSIS
async_daemon(
unsigned long iod_num,
unsigned long magic);
PARAMETERS
Specifies the number of I/O threads to run. For Tru64 UNIX, this is 950410. If a different value is used, seven NFS I/O threads are run.
DESCRIPTION
The use of the async_daemon() function is not supported in customer applications, and the interface is subject to change without notice.
It is intended for use solely by nfsiod(8).
The async_daemon() function starts iod_num NFS I/O kernel threads that are used to improve NFS I/O performance. This function does not
return to the caller, but remains in the kernel to provide additional support for NFS over TCP.
RETURN VALUES
The async_daemon function has no successful return. In fact, it frees the text and data segments associated with the calling program so
there is nothing to return to. When interrupted by a KILL signal, the I/O threads are terminated and the process exits. If the async_dae-
mon function encounters errors, , -1 is returned and errno is set to indicate the error.
ERRORS
If the async_daemon() function fails, errno may be set to the following value: The async_daemon function has already been called by another
process. The caller is not the superuser. More than 64 I/O threads were requested. The kernel memory allocator has no memory.
RELATED INFORMATION
Functions: nfssvc(2)
Commands: nfsiod(8) delim off
async_daemon(2)
Hello,
My problem thus follows:
I am running a server which allows users to connect on UDP, not TCP.
There is a certain hacker, whom I have the IP of, who keeps crashing the server. I simply want to block him from accessing my box at all. I added him to the hosts.deny file, but am not sure if... (4 Replies)
Discussion started by: Phobos
4 Replies
2. Post Here to Contact Site Administrators and Moderators
Hello !
I seem to have the same problem as in https://www.unix.com/ip-networking/91203-inaddr_any-opposite.html#post302262417
But I can't find a solution.
I have a UDP server socket bound to 0.0.0.0. The server hosts the addresses IP1, IP2 and IP3. I get an incoming request to IP1. I use... (1 Reply)
Like many UNIX users, there is a small team that is connected to UNIX (under the same UNIX user) via putty from a Windows PC.
Is there a way, once under UNIX, to know the address of the originating computer or anything that can differentiate initial users ? (7 Replies)
Hi,
Anyone can tell me how to get the number of NFS threads RUNNING on the system for Solaris 10? Someone told me for Solaris 9, the method is "echo "*svc$<svcpool" | adb -k. But, I've tried to google the method for Solaris 10 and did not find the corresponding method, please help... (1 Reply)
There have been a lot of threads about how to find processes that are using a specific port on an AIX server. After long hours of research and reading countless "you can't do that" responses, I finally found the answer.
YES IT CAN BE DONE! YES ITS EASY. NO, I DON'T KNOW WHY NO ONE GETS THIS... (2 Replies)
Hi all,
I got an application that is running on SUSE Linux. I would like to get some data about the number of TCP segments retransmission on a particular interface. Is there any way I can get that?
Thanks, (2 Replies)
Hi All,
We have a T5140 server which has 128 threads in total. Is it possible to reduce the number of threads per core through some configuration changes? I am sorry for being so naive but I am one on this.
Why would I like to do this? Unfortunately we have this for an Oracle Database Server... (6 Replies)
Hello,
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.
In the boot.log file i see
Starting NFS quotas: Cannot register service:... (2 Replies)