05-15-2005
i want a UDP Client receiving program
Hi
I want a UDP client receiving program. Here is the scenario. The client has to listen to the UDP server and has to acknowledge back on receiving data from the server. Can anyone help me out.
regards,
Nirmala
10 More Discussions You Might Find Interesting
1. Filesystems, Disks and Memory
I'm working on a project to extract some information from archive file. I ran my program through MFCobol animator and I'm receiving
a status code of 39(file not compatible) when opening the file for input. I have tried just about everything, rebuild, convert, etc. but
I receive the same message.... (6 Replies)
Discussion started by: bigdawg
6 Replies
2. Programming
i came acors this coding when surfin the net.this code works perfectly.but as i am new to this socket programming i need sm coments quoted on it or explanation regarding this source code.
i have prb understanding the server.c i have posted it below
can u guys help me !!!!
cheerZ
The... (4 Replies)
Discussion started by: mathu
4 Replies
3. Programming
Hi,
Am very new to socket programming.
When we use UDP sockets to communicate between two processess,
will both the client/server socket be able to send/recv ?
meaning can sendto()/ recvfrom() be used on both server and client?
It could be useful even if anybody provide some link on socket... (1 Reply)
Discussion started by: rvan
1 Replies
4. Programming
hi guys,
I need the code for a server client registration form.The server must ask for authentication .Then the client would send in data. This is stored in a file .The server sends back a receipt to the client as part of the payment done.
plz can some 1 get me the code... (9 Replies)
Discussion started by: pip3r
9 Replies
5. Programming
can u help me? i need the program code in C to perform Simple File Transfer in linux.in this forum i found the server program,inw i need the client program ASAP.
Thanx. (1 Reply)
Discussion started by: harshi
1 Replies
6. Programming
hi,
I am writing one packet receiving program using libpcap library.
Now, I want to check port is already using or not.
how to check in receiver program..
If normal program, bind return value we can able to check the port using or not.
but, in pcap program how can i check?
thank... (1 Reply)
Discussion started by: ram.sj
1 Replies
7. IP Networking
I'm looking for a couple high level pointers to writing a UDP server that will be acknowledging data at a rate of approximately twelve packets every second and will be running on and older but more or less dedicated Solaris 9 box.
Acknowledging the data packets is relatively simple, after... (2 Replies)
Discussion started by: allbread
2 Replies
8. Programming
Hi,
I have a situation where i need to communicate a linux client with a windows server, I am using a UDP socket communication channel. I am able to send packets from my linux clients to the windows server but unable to receive any data packet from the server. Do i need to make any setting in... (0 Replies)
Discussion started by: John20
0 Replies
9. Programming
I try to initial a UDP client from threading, but it doesn't work? why?
These codes from the textbook
#define ECHOMAX 255 /* Longest string to echo */
#define TIMEOUT_SECS 2 /* Seconds between retransmits */
#define MAXTRIES 5 /* Tries before giving up */... (3 Replies)
Discussion started by: sehang
3 Replies
10. Programming
I am having problems receiving data from a remote server. It seems that I can send an HTTP request to any host such as http://www.google.com, but I can't get a reply.
I'm sending the host a HTTP 1.0 request that is formatted as such:
GET / HTTP/1.0
Host: http://www.google.com
Connection:... (0 Replies)
Discussion started by: shubham92
0 Replies
nfsd(8) System Manager's Manual nfsd(8)
NAME
nfsd - The remote NFS compatible server
SYNOPSIS
/usr/sbin/nfsd [-t num_tcpthreads] [-u num_udpthreads]
The following form of the nfsd command is not recommended and is supported only for backward compatibility:
/usr/sbin/nfsd [numthreads]
FLAGS
Specifies a number of TCP server threads (per RAD) to spawn. A value of 8 is recommended as a start. Specifies a number of UDP server
threads (per RAD) to spawn. A value of 8 is recommended as a start.
DESCRIPTION
The nfsd daemon runs on a server machine to service NFS requests from client machines. The daemon spawns a number of server threads that
process NFS requests from client machines. At least one server thread must be running for a machine to operate as a server.
There are two types of server threads: a server thread that processes NFS requests sent using TCP and a server thread that processes NFS
requests sent using UDP. This is necessary because the kernel paths for UDP and TCP NFS messages are different. The -t option specifies
the number of TCP threads to run and the -u option specifies the number of UDP threads to run.
On systems that support Cache Coherent NUMA, the number of threads is per Resource Affinity Domain (RAD). As you add RADs, the NFS server
will automatically scale by creating additional threads. NFS requests are processed by a particular RAD based on the file being accessed;
this confines cached information about a file to a single RAD for efficiency. See numa_intro(3) for more information on the NUMA architec-
ture.
If you use the SysMan Menu to configure NFS, it sets the default at 8 UDP and 8 TCP threads. However, a user can have any number of TCP
and UDP nfsd threads running up to a maximum of 128 threads. The optimal number of TCP server threads and UDP server threads depends on
many factors. See nfsiod(8) for more information.
The server threads are implemented as kernel threads; they are part of Process ID 0, not the nfsd process. The ps axml command displays
idle server threads under PID 0. Idle threads will be waiting on nfs_udp_wait or nfs_tcp_wait. Therefore, if 16 server threads are config-
ured, only one nfsd process is displayed in the output from the ps command, although 16 server threads are available to handle NFS
requests.
Files that are larger than 2 gigabytes are exported as 2 gigabyte files when accessed by NFS Version 2. NFS Version 2 is a 32-bit proto-
col, therefore, the size and offset fields are 32-bit quantities (on Alpha UFS they are 64-bit quantities). Use caution when accessing
files larger than 2 gigabytes from NFS clients.
EXAMPLES
In the following example, 16 threads are run (8 for TCP and 8 for UDP): nfsd -t 8 -u 8
FILES
Specifies the command path Specifies the file for logging startup errors (before the server threads are started). Specifies the file for
logging NFS errors (after the server threads are started).
RELATED INFORMATION
Commands: mount(8), mountd(8), nfsconfig(8), nfsstat(8), portmap(8)
System calls: nfssvc(2) delim off
nfsd(8)