Hi Gurus!
I recently got my shell account (HP UX v11) created by our sysadmin and am having problem deleting with the backspace key.
After doing some reading, I believe I need to enter a custom "STTY..." statement in my profile.
Can someone please help me with the correct "STTY" sequence... (3 Replies)
Sorry to I am not familiar with script writing ,
attach is the /etc/profile in my system , we have limit each user can only have one login in the system . When the user login , if the system found the user have a dead process in the system , the system will confirm the user to kill the previous... (1 Reply)
Hello
I really wonder what's trap in etc/profile and in each user .profile.
I try to google for it but I think I have no luck. Mostly hit is SNMP traps which I think it is not the same thing.
I want to know ...
1. What's a "trap 2 3" means and are there any other value I can set... (4 Replies)
hi guys
In a few days I will be working in a new Job my new chief told I will be using Solaris and since I know Centos-Red Hat-Fedora
I would like to know if Solaris is that different from Centos and my other linux Flavors...
by the way any good solaris manual
thanks a lot (1 Reply)
Hi,
happy new year.
on AIX 6.1 , for user oracle , there are two files :
bash_profile and .profile
I do not know which one is executed when login ? How to know ,
More over in both of them we have :
in .profile :
ORACLE_HOME=/appli/oracle/product/10.2.0/db_1... (5 Replies)
Good evening everybody,
I like to have my prompt like that : $
Therefore I had the line below in the .bash_profile file:
PS1="\$"
Now I would like to have something like that when I log as root : #
and adding PS1="\#" is definitely not working...
Any idea how to do that?
Many... (4 Replies)
Hi Gurus,
Recently we have migrated our servers from AIX to Linux. Most of the scripts written in AIX server are sourcing environment variables using .profile file. Now we have the following options:
1. Change all the scripts where ever .profile is being used and replace it with... (14 Replies)
Discussion started by: svajhala
14 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