02-27-2009
You're going to need to be root in order to set up these files.
10 More Discussions You Might Find Interesting
1. UNIX for Advanced & Expert Users
Changed from a broken Switch to a working HUB everyting else in my network is ok after the change but not my RS/6000! It refuses to get connected, get time out on Pings both ways - strange?
Could it be some problem with ARP?:confused: (2 Replies)
Discussion started by: jolun
2 Replies
2. UNIX for Dummies Questions & Answers
Having problem in connecting my gui java program to postgreaql database. I first used setenv classpath /home/share/postgresql/java/postgresql.jar:proj1, where proj1 is my folder conatining all java and class file, to set classpath. Then javac *.java. Then java proj1.Login. It gives me... (2 Replies)
Discussion started by: uci
2 Replies
3. IP Networking
Dear Member:-
Kindly be I am facing a problem with my open Solaris release b101
1- vi /etc/hostname.reg0
This is my IP address xx.xx.xx.xx
2- vi /etc/netmasks
This is my subnet mask
3- vi /etc/defaultrouter
This is my gateway
4- vi /etc/resolv.conf
This is my DNS written with this way ... (2 Replies)
Discussion started by: dellroxy
2 Replies
4. Solaris
Hi everyone,
I am hoping anyone of you could help me in this weird problem we have in 1 of our Solaris 10 servers. Lately, we have been having some ftp problems in this server. Though it can ping any server within the network, it seems that it can only ftp to a select few. For most servers, the... (4 Replies)
Discussion started by: labdakos
4 Replies
5. Solaris
Hello colleague,
Development department is deploying some applications on solaris machine but hence all connection goes down.
Our all network connection files are correct but we can't connect with our gw. Only we can ping localhost and assigned ip address.
I don't want to reboot for... (4 Replies)
Discussion started by: getrue
4 Replies
6. Linux
Hi, I installed linux Fedora on a virtual machine, but the network connection is not working. All firewalls are off. Any ideas what is the problem? I am using WiFi.
Thanks in advance!
Regards,
Atanas (2 Replies)
Discussion started by: apenkov
2 Replies
7. Solaris
hi,
I'm setting up a home lab and I am having problems keeping my connection open on putty. every time i leave it for about 10 seconds and come back I keep having to re-connect. I'm more of a AIX person and trying to get more fimilar with Sun but some of the commands I am trying to run to diag... (2 Replies)
Discussion started by: vpundit
2 Replies
8. Programming
I have started reading the book Unix Network Programming, Volume 1: The Sockets Networking API. I downloaded all the source code and the readme says I must make the files.
zuro@zuro:~/book/unpv12e$ cd lib
zuro@zuro:~/book/unpv12e/lib$ make
gcc -g -O2 -D_REENTRANT -Wall -c -o... (5 Replies)
Discussion started by: xuro
5 Replies
9. Programming
I have started reading the book Unix Network Programming, Volume 1: The Sockets Networking API. I downloaded all the source code and performed all the steps present in README file.Now when i compile my first program it give the following error.
sainandan@nandan:~/unpv13e/intro$ ./daytimetcpcli... (1 Reply)
Discussion started by: bsainandan
1 Replies
10. Solaris
Hi,
Recently we faced awkward situation where we cannot connect to Oracle DB that hosted in Solaris server intermittently and it timeout eventually. The server seems fine. We can putty to server like normal but when try do prstat, it takes time and come out Please Wait.. for a while. When we go... (1 Reply)
Discussion started by: tharmendran
1 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)