08-05-2013
/bin/find, because in my family I am the one who is supposed to know where all the stuff is that someone has misplaced.
8 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
How do I send a file as an attachment (gzip file) on a Unix system ? Using sendmail.
Please help me.
:confused: (3 Replies)
Discussion started by: lacca
3 Replies
2. UNIX for Dummies Questions & Answers
When I log on to my unix session I have a default location. But I need to navigate 3 directories up then 6 directories down to where I want to be. There must be a way to create some sort of short cut from my defeault location to my required location. Can anyone help? (4 Replies)
Discussion started by: jjaggii
4 Replies
3. Shell Programming and Scripting
Dear All,
I'm new in unix system, when i'm try to get file from Unix system using FTP .
I using "get" command for transfer file from unix to windows folder but, there error happened , message is :
get filename
ERROR : not an SCCS file <col>
how can I transfer this file ..??
and how... (1 Reply)
Discussion started by: heru_90
1 Replies
4. Shell Programming and Scripting
Dear All,
I want try to using unix,till now i just download 2 Iso file from 5 iso file of Sun Solaris 10. But know I just using unix sun solaris 6.5 that using in my company and I have root password. But some time I'm worry to using root password cos I don't have good basic knowladge about Unix... (1 Reply)
Discussion started by: heru_90
1 Replies
5. Programming
Before i start doing something, I wanted to know whether the approach to compare XML file with UNIX file system structure. I have a pre-configured file(contains a list of paths to executables) and i need to check against the UNIX directory structure. what are the various approches should i use ? I... (6 Replies)
Discussion started by: shafi2all
6 Replies
6. UNIX for Dummies Questions & Answers
which one is correct explanaton for unix file system
a. Explaining about directory hierarchy or
b. Explaining about boot block , super block? (1 Reply)
Discussion started by: gwgreen1
1 Replies
7. UNIX for Advanced & Expert Users
Dear All,
We are using COMPAQ DS -10 machines with UNIX 4.0F
System is behaving abnormal some directories shows full and they should not be . here is df -k output of a machines
file system----1024 block-----used--available--capacity--mounted on
/dev/rz17h-----8680793----- 1 --- ... (1 Reply)
Discussion started by: akash.jahangir
1 Replies
8. Shell Programming and Scripting
We would be migrating UNIX file system to Linux file system.
We do have many directory and sub directories with files.
after migrating unix to linux file system , i want to make sure all the files has been copied ? What would be the best approach to validate directory ,sub-directory and file... (1 Reply)
Discussion started by: balajikalai
1 Replies
LEARN ABOUT OPENDARWIN
unix
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.
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