Login or Register to Ask a Question and Join Our Community

Sponsored Content
Full Discussion: fd passing between Independent processes using unix domain sockets
Operating Systems HP-UX fd passing between Independent processes using unix domain sockets Post 66176 by Perderabo on Friday 11th of March 2005 08:07:18 AM
Old 03-11-2005
After your TCP/Server passes the fd to the Logic Server, the TCP/Server must issue a close() on the fd. This will not perform a shutdown on the socket. Later when the Logic Server dies, the exit code will also close() the socket. This will be the final process with a pointer to the socket's file table entry. So this close() will trigger a shutdown on the socket.
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Association b/w sockets & processes

Hi, Is there any way i can know the association between sockets and the processes which created them. :confused: (5 Replies)
Discussion started by: soorajmu
5 Replies

2. 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

3. 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

4. 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

5. 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

6. Shell Programming and Scripting

Position independent Parameter passing

Hi all, When parameters are passed to the shell script, they are dereferenced by their position. For example, I call myTest.sh and pass two parameters param1 and param2 as following: ./myTest.sh param1 param2 In the script, myTest.sh, I refer to first parameter (param1 ) as $1 and second... (1 Reply)
Discussion started by: sonaluphale
1 Replies

7. What is on Your Mind?

When Unix will have a singe version, platform independent OS

I wonder when UNIX will be a OS, will have a single version. (1 Reply)
Discussion started by: abhishek0216
1 Replies

8. UNIX for Advanced & Expert Users

UNIX domain sockets vs FIFOs

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

9. Shell Programming and Scripting

Finding the age of a unix process, killing old processes, killing zombie processes

I had issues with processes locking up. This script checks for processes and kills them if they are older than a certain time. Its uses some functions you'll need to define or remove, like slog() which I use for logging, and is_running() which checks if this script is already running so you can... (0 Replies)
Discussion started by: sukerman
0 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

LEARN ABOUT MOJAVE

net::server::proto::unix5.18

Net::Server::Proto::UNIX(3)				User Contributed Perl Documentation			       Net::Server::Proto::UNIX(3)

NAME

       Net::Server::Proto::UNIX - Net::Server UNIX protocol.

SYNOPSIS

       See Net::Server::Proto.

DESCRIPTION

       Protocol module for Net::Server.  This module implements the UNIX SOCK_STREAM socket type.  See Net::Server::Proto.

       Any sockets created during startup will be chown'ed to the user and group specified in the starup arguments.

PARAMETERS

       The following paramaters may be specified in addition to normal command line parameters for a Net::Server.  See Net::Server for more
       information on reading arguments.

       unix_type
	   Can be either SOCK_STREAM or SOCK_DGRAM (default is SOCK_STREAM).  This can also be passed on the port line (see Net::Server::Proto).

	   However, this method is deprecated.	If you want SOCK_STREAM - just use proto UNIX without any other arguments.  If you'd like
	   SOCK_DGRAM, use the new proto UNIXDGRAM.

METHODS

       NS_unix_path/NS_unix_type
	   In addition to the standard NS_ methods of Net::Server::Proto classes, the UNIX types also have legacy calls to NS_unix_path and
	   NS_unix_type.

	   Since version 2.000, NS_unix_path is simply an alias to NS_port.  NS_unix_type is now redundant with NS_proto.

	   These methods were missing between version 2.000 and 2.003 but have been returned as legacy bridges.

QUICK PARAMETER LIST

	 Key		   Value		    Default

	 # deprecated UNIX socket parameters
	 unix_type	   (SOCK_STREAM|SOCK_DGRAM) SOCK_STREAM
	 port		   "filename"		    undef

	 # more recent usage
	 port		   "filename / UNIX"
	 port		   "filename / UNIXDGRAM"

LICENCE

       Distributed under the same terms as Net::Server

perl v5.18.2							    2012-06-06					       Net::Server::Proto::UNIX(3)
All times are GMT -4. The time now is 01:01 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy