06-29-2004
Thanks for your reply rhfrommn.
The UNIX version is Sinix 5.41. LAN users connect to this box using terminal emulation software. I need (for networking reasons) to alter the ip address of the UNIX server so that it fits in with a specific ip address range and holds that address after rebooting and then re-configure the terminal emulation software to connect to the new ip address.
IF anyone is familiar with this UNIX version and can outline how this should be done I would be forever in your debt!!
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
HELP!! How do you change the network setting from auto-duplex to 100 Base T Full Duplex in Red HaT? (1 Reply)
Discussion started by: johnlong
1 Replies
2. Linux
I've been looking for documentation on how to stop this behavior. I have two nics in my system.
eth0: configured manually and as a dhcp server for the local network
eth1: configured w/ dhcp enabled connected to router
dns server addresses keep getting reset every few minutes. i suspect... (0 Replies)
Discussion started by: rbetzen
0 Replies
3. Solaris
I have problem with network settings.
Where i can find network config ? I'm newbie, but i very want learn this OS.
I find :
/etc/hostname.<interface>
/etc/netconfig
/etc/netmasks
/etc/networks
/etc/inet/hosts
But where i can write my IP-address and after reboot i be know that my server... (2 Replies)
Discussion started by: jess_t03
2 Replies
4. IP Networking
hello i have a ubuntu ssh server that i can acess from any of my comnputers but only if they are on the same wireless network as the server. i tested trhis my tehtehring my samsung blackjack to my windows partition and installing openssh to windows it works when windows is on the wireless but no... (1 Reply)
Discussion started by: old noob
1 Replies
5. HP-UX
Hello everyone..
While printing through command line, we can set printing option with -o <lanscape/portrait> to print file in required mode.
But i want to know is there any way we can set this as default behaviour for this printer?
After configuration any script we can modify for this... (0 Replies)
Discussion started by: laxmikant
0 Replies
6. UNIX for Dummies Questions & Answers
Hello Unix Gurus Who I Hope Reads This,
I have quasi-inherited control over a Linux cluster at a university research lab. The post-doc that set it up is gone, and the person in charge of administering the cluster doesn't know a ton about Linux. Amongst other things, I want to use the cluster... (0 Replies)
Discussion started by: mbl
0 Replies
7. Solaris
Hi
i have created a solaris zone but have not yet connected any network cables for this new zone,
can i set the zone up without running the command 'add net' and not adding an ip or physical interface?
i tried to add dummy internet settings and get this
zonecfg:coddr> add net... (4 Replies)
Discussion started by: newbiesolaris10
4 Replies
8. Shell Programming and Scripting
Hello, Newbie question on scripting - I'm looking to create a simple script that will work on RHEL5 that will adjust the network settings: ip address, default gateway, and subnet mask. If anything else needs to be done (service network stop / start) or should be done to make settings active - I... (4 Replies)
Discussion started by: rojizo
4 Replies
9. UNIX for Dummies Questions & Answers
Hi,
I have inherited a Motorola System V R32V3.2 system. The system works fine, but we need to change the network settings. I've changed the IP address successfully, however I'm lost on the gateway and subnet mask. I've changed the default gateway using route -g10.0.8.1, but it changes back to... (7 Replies)
Discussion started by: Tilmar
7 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