5 More Discussions You Might Find Interesting
1. Open Source
Hi All,
I have a current Process that runs "windows script " for the file movement that needs to changed to a "DataStage Process (Using shell script )"
Source :Text file is getting generated as part of Datastage Jobs processes and resides in a shared drive (Unix server)
Target :ftp... (2 Replies)
Discussion started by: developer.dwh9
2 Replies
2. What is on Your Mind?
Are we having sat-sun holiday for unix forum?
I am just thinking there are no new things to explore on sat-sun. It looks like holiday for this site also....:D (1 Reply)
Discussion started by: pamu
1 Replies
3. IP Networking
In the following Unix Tip from Unix Guru Universe, are there some typos?
Specifically, should:
"From hosts(user:deepak)" be "From host2(user:deepak)"? (I'm almost 100% certain it should)
"rlogin hosts.domain.com -l paul" be "rlogin host2.domain.com -l paul"?
Some related... (0 Replies)
Discussion started by: RandyKramer
0 Replies
4. Post Here to Contact Site Administrators and Moderators
Of late, when i start www.unix.com my system is
going to 100% CPU and takes lot of time to get
the information. I think this is happening after
adding the graphics on the page. Has anyone seen
this problem..Sorry to post this here.. (6 Replies)
Discussion started by: sssow
6 Replies
5. Post Here to Contact Site Administrators and Moderators
PUZZLED:
How can I search for posts on 'VI' if by the new rules (or maybe they are old) I get the messge:
"The search term you specified (vi) is under the minimum word length (3) and therefore will not be found. Please make this term longer.
If this term contains a wildcard, please make... (13 Replies)
Discussion started by: sierra_aar
13 Replies
UNIX(4) BSD Kernel Interfaces Manual UNIX(4)
NAME
unix -- UNIX-domain protocol family
SYNOPSIS
#include <sys/types.h>
#include <sys/un.h>
DESCRIPTION
The UNIX-domain protocol family is a collection of protocols that provides local (on-machine) interprocess communication through the normal
socket(2) mechanisms. The UNIX-domain family supports the SOCK_STREAM and SOCK_DGRAM socket types and uses filesystem pathnames for address-
ing.
ADDRESSING
UNIX-domain addresses are variable-length filesystem pathnames of at most 104 characters. The include file <sys/un.h> defines this address:
struct sockaddr_un {
u_char sun_len;
u_char sun_family;
char sun_path[104];
};
Binding a name to a UNIX-domain socket with bind(2) causes a socket file to be created in the filesystem. This file is not removed when the
socket is closed--unlink(2) must be used to remove the file.
The UNIX-domain protocol family does not support broadcast addressing or any form of ``wildcard'' matching on incoming messages. All
addresses are absolute- or relative-pathnames of other UNIX-domain sockets. Normal filesystem access-control mechanisms are also applied
when referencing pathnames; e.g., the destination of a connect(2) or sendto(2) must be writable.
PROTOCOLS
The UNIX-domain protocol family is comprised of simple transport protocols that support the SOCK_STREAM and SOCK_DGRAM abstractions.
SOCK_STREAM sockets also support the communication of UNIX file descriptors through the use of the msg_control field in the msg argument to
sendmsg(2) and recvmsg(2).
Any valid descriptor may be sent in a message. The file descriptor(s) to be passed are described using a struct cmsghdr that is defined in
the include file <sys/socket.h>. The type of the message is SCM_RIGHTS, and the data portion of the messages is an array of integers repre-
senting the file descriptors to be passed. The number of descriptors being passed is defined by the length field of the message; the length
field is the sum of the size of the header plus the size of the array of file descriptors.
The received descriptor is a duplicate of the sender's descriptor, as if it were created with a call to dup(2). Per-process descriptor
flags, set with fcntl(2), are not passed to a receiver. Descriptors that are awaiting delivery, or that are purposely not received, are
automatically closed by the system when the destination socket is closed.
The effective credentials (i.e., the user ID and group list) the of a peer on a SOCK_STREAM socket may be obtained using the LOCAL_PEERCRED
socket option. This may be used by a server to obtain and verify the credentials of its client, and vice versa by the client to verify the
credentials of the server. These will arrive in the form of a filled in struct xucred (defined in sys/ucred.h). The credentials presented
to the server (the listen(2) caller) are those of the client when it called connect(2); the credentials presented to the client (the
connect(2) caller) are those of the server when it called listen(2). This mechanism is reliable; there is no way for either party to influ-
ence the credentials presented to its peer except by calling the appropriate system call (e.g., connect(2) or listen(2)) under different
effective credentials.
SEE ALSO
socket(2), intro(4)
"An Introductory 4.3 BSD Interprocess Communication Tutorial", PS1, 7.
"An Advanced 4.3 BSD Interprocess Communication Tutorial", PS1, 8.
BSD
June 9, 1993 BSD