Sponsored Content
Full Discussion: UNIX domain sockets vs FIFOs
Top Forums UNIX for Advanced & Expert Users UNIX domain sockets vs FIFOs Post 302179473 by ramen_noodle on Thursday 27th of March 2008 09:03:05 PM
Old 03-27-2008
^^Heh^^ There's a sad story there. Smilie

I don't find unix domain sockets that terrible to use and they are still the best local way of bidirectional communication and concurrent data access between many processes.
 

10 More Discussions You Might Find Interesting

1. IP Networking

Unix Domain

hello, how can we create a domain in unix operating systems. By domain i mean which is used to maintain remote user logins and etc. cheers (1 Reply)
Discussion started by: vibhory2j
1 Replies

2. UNIX for Dummies Questions & Answers

UNIX in MS Win2003 Domain

Hi, Can I make a UNIX or LINUX machine a member of MS Active Directory 2003? How? Regards Leo (4 Replies)
Discussion started by: Teamplay
4 Replies

3. UNIX for Dummies Questions & Answers

Adding a Unix machine to the domain

Hiya, what is the exact command to add a Unix machine to the existing domain? Is this command different for Linux/HP-Ux? thanks (3 Replies)
Discussion started by: Wize
3 Replies

4. HP-UX

fd passing between Independent processes using unix domain sockets

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

5. Programming

Praying for help: FIFOs, IPC

omg i need help so bad. I've been working on a school project for what seems like an eternity and i'm close to deadline. Using FIFO's (i ahve to) to communicate between parent and child proc's. Right now I'm stuck on a read/write. fifomsg is a struct with int length and char message fields. ... (5 Replies)
Discussion started by: Funktar
5 Replies

6. Programming

forks, ipc, fifos, update issues...

Hi, so I've got this program("main") that fork executes another ("user"). These programs communicate through fifos. One communication is a spawn call, where user passes an executable, main forks and executes it. So, I'm keeping track of all my processes using a task table. After the fork (for... (6 Replies)
Discussion started by: Funktar
6 Replies

7. Linux

A little help understanding FIFOs?

This isn't strictly a Linux question, but... I've been working on a project to archive some streaming media for time shifting using 'mplayer' and have been using FIFOs to archive in Ogg Vorbis format: mkfifo program_name.wav (mplayer -ao pcm -aofile program_name.wav &)... (0 Replies)
Discussion started by: deckard
0 Replies

8. UNIX for Advanced & Expert Users

tar and fifos

How can I make tar read data from a fifo, instead of storing it as a fifo? (8 Replies)
Discussion started by: Corona688
8 Replies

9. UNIX for Advanced & Expert Users

UNIX Message Queues vs. Sockets

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

10. UNIX for Dummies Questions & Answers

what is the advantage of unix sockets?

Hi, i understood that there are several type of sockets: TCP, UDP & Unix. i wondered, what is the performance advantages of unix socket of the other types? isn't it equal to use UDP with localhost as destination over unix socket? Thanks in advance, Sariel (1 Reply)
Discussion started by: sarielz
1 Replies
SOCKET(P)						     POSIX Programmer's Manual							 SOCKET(P)

NAME
socket - create an endpoint for communication SYNOPSIS
#include <sys/socket.h> int socket(int domain, int type, int protocol); DESCRIPTION
The socket() function shall create an unbound socket in a communications domain, and return a file descriptor that can be used in later function calls that operate on sockets. The socket() function takes the following arguments: domain Specifies the communications domain in which a socket is to be created. type Specifies the type of socket to be created. protocol Specifies a particular protocol to be used with the socket. Specifying a protocol of 0 causes socket() to use an unspecified default protocol appropriate for the requested socket type. The domain argument specifies the address family used in the communications domain. The address families supported by the system are imple- mentation-defined. Symbolic constants that can be used for the domain argument are defined in the <sys/socket.h> header. The type argument specifies the socket type, which determines the semantics of communication over the socket. The following socket types are defined; implementations may specify additional socket types: SOCK_STREAM Provides sequenced, reliable, bidirectional, connection-mode byte streams, and may provide a transmission mechanism for out-of-band data. SOCK_DGRAM Provides datagrams, which are connectionless-mode, unreliable messages of fixed maximum length. SOCK_SEQPACKET Provides sequenced, reliable, bidirectional, connection-mode transmission paths for records. A record can be sent using one or more output operations and received using one or more input operations, but a single operation never transfers part of more than one record. Record boundaries are visible to the receiver via the MSG_EOR flag. If the protocol argument is non-zero, it shall specify a protocol that is supported by the address family. If the protocol argument is zero, the default protocol for this address family and type shall be used. The protocols supported by the system are implementation- defined. The process may need to have appropriate privileges to use the socket() function or to create some sockets. RETURN VALUE
Upon successful completion, socket() shall return a non-negative integer, the socket file descriptor. Otherwise, a value of -1 shall be returned and errno set to indicate the error. ERRORS
The socket() function shall fail if: EAFNOSUPPORT The implementation does not support the specified address family. EMFILE No more file descriptors are available for this process. ENFILE No more file descriptors are available for the system. EPROTONOSUPPORT The protocol is not supported by the address family, or the protocol is not supported by the implementation. EPROTOTYPE The socket type is not supported by the protocol. The socket() function may fail if: EACCES The process does not have appropriate privileges. ENOBUFS Insufficient resources were available in the system to perform the operation. ENOMEM Insufficient memory was available to fulfill the request. The following sections are informative. EXAMPLES
None. APPLICATION USAGE
The documentation for specific address families specifies which protocols each address family supports. The documentation for specific pro- tocols specifies which socket types each protocol supports. The application can determine whether an address family is supported by trying to create a socket with domain set to the protocol in ques- tion. RATIONALE
None. FUTURE DIRECTIONS
None. SEE ALSO
accept() , bind() , connect() , getsockname() , getsockopt() , listen() , recv() , recvfrom() , recvmsg() , send() , sendmsg() , setsock- opt() , shutdown() , socketpair() , the Base Definitions volume of IEEE Std 1003.1-2001, <netinet/in.h>, <sys/socket.h> COPYRIGHT
Portions of this text are reprinted and reproduced in electronic form from IEEE Std 1003.1, 2003 Edition, Standard for Information Technol- ogy -- Portable Operating System Interface (POSIX), The Open Group Base Specifications Issue 6, Copyright (C) 2001-2003 by the Institute of Electrical and Electronics Engineers, Inc and The Open Group. In the event of any discrepancy between this version and the original IEEE and The Open Group Standard, the original IEEE and The Open Group Standard is the referee document. The original Standard can be obtained online at http://www.opengroup.org/unix/online.html . IEEE
/The Open Group 2003 SOCKET(P)
All times are GMT -4. The time now is 02:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy