05-26-2011
TCP and UDP are different facilities under IP, but UNIX sockets are local to the host and simpler, like pipes.
TCP creates a reliable one on one session between a client and server, with full duplex streams of data.
UDP is a user-level packet facility, without 'reliability' but with broadcast and mixed correspondent capability as well as a 'connection' facility, just a fd with a filter and default correspondent. For instance, DNS uses UDP, and a DNS server sits there receiving packets, and for every packet in, makes a packet out. The packet in may be a request for local data, a request for remote data or a response to a past inquiry sent by this server to other DNS servers. The server sends a response to the inquiry, or if tasked with recursion, an inquiry for the inquiry. For responses, the server sends them on to the requestor and caches them locally. The server does all this with one not-connected UDP socket.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
? (1 Reply)
Discussion started by: 98_1LE
1 Replies
2. HP-UX
Hi,
I am having some error handling issues with and fd passed between Independent processes using unix domain sockets (On HPUX).
Here is the scnerio
=================
Step 1: TPC/Client (connect()) ---Connects to ------TCP/Server(Gateway) (server gets fd)
Step 2: ... (2 Replies)
Discussion started by: Debasisb2002
2 Replies
3. UNIX for Advanced & Expert Users
If I use sockets for IPC, and can easily distribute my applications.
UNIX Message Queues are local to the processor.
As I understand it, Message Queues still incur system call overhead, just like socket calls.
What advantage does a UNIX Message Queue provide versus a TCP or UDP Socket,... (2 Replies)
Discussion started by: zen29sky
2 Replies
4. UNIX for Advanced & Expert Users
Is there a performance advantage of one of these over the other? Obviously, it makes no sense to use normal TCP sockets or UDP sockets w/ the overhead they carry. But what about UNIX domain sockets vs FIFOs? I'd think they'd be very similar, in terms of performance and in terms of how they're... (2 Replies)
Discussion started by: mgessner
2 Replies
5. Shell Programming and Scripting
Hi
I'm reading <learning the bash shell>. And in the section - 3.1. The .bash_profile, .bash_logout, and .bashrc Files
bash allows two synonyms for .bash_profile: .bash_login, derived from the C
shell's file named .login, and .profile, derived from the Bourne shell and Korn
shell files... (1 Reply)
Discussion started by: password636
1 Replies
6. Solaris
What are the advantages for Sun Fire 490 over Sun Fire 480 R just from a server performance perspective? Or, are they both just about the same? (1 Reply)
Discussion started by: jtamminen
1 Replies
7. Red Hat
Hi guys, new user here, so please be gentle.
I need to build a lot of servers at work on a weekly basis with various versions of RH and additional applications.
We use PXE/Kickstart to do this with selections made from a simple menu structure.
However, I keep hearing about Cobbler and... (0 Replies)
Discussion started by: hankpym
0 Replies
LEARN ABOUT SUNOS
in.daytimed
in.daytimed(1M) System Administration Commands in.daytimed(1M)
NAME
in.daytimed - UDP or TCP daytime protocol service daemon
SYNOPSIS
in.daytimed
FMRI
svc:/internet/daytime:default
DESCRIPTION
FMRI stands for Fault Management Resource Identifier. It is used to identify resources managed by the Fault Manager. See fmd(1M) and
smf(5).
The in.daytimed service provides the server-side of the daytime protocol. This protocol is used for debugging and bandwidth measurement and
is available on both TCP and UDP transports, through port 13.
The in.daytimed service is an inetd(1M) smf(5) delegated service. The in.daytimed detects which transport is requested by examining the
socket it is passed by the inetd daemon.
TCP-based service
Once a connection is established, the in.daytimed generates the current date and time in ctime(3C) format as 7-bit ASCII and sends it
through the connection. The server then closes the connection. Any data received from the client side of the connection is discarded.
UDP-based service
The in.daytimed listens for UDP datagrams. When a datagram is received, the server generates the current date and time in ctime(3C)
format as 7-bit ASCII and inserts it in a UDP datagram sent in response to the client's request. Any received data is ignored.
ATTRIBUTES
See attributes(5) for descriptions of the following attributes:
+-----------------------------+-----------------------------+
| ATTRIBUTE TYPE | ATTRIBUTE VALUE |
+-----------------------------+-----------------------------+
|Availability |SUNWcnsu |
+-----------------------------+-----------------------------+
|Interface Stability |Evolving |
+-----------------------------+-----------------------------+
SEE ALSO
inetd(1M), attributes(5), smf(5)
RFC 867
SunOS 5.10 23 Aug 2004 in.daytimed(1M)