File: finding-network-addr.txt

package info (click to toggle)
dmtcp 2.6.0-1
  • links: PTS, VCS
  • area: main
  • in suites: sid
  • size: 6,496 kB
  • sloc: cpp: 33,592; ansic: 28,099; sh: 6,735; makefile: 1,950; perl: 1,690; python: 1,241; asm: 138; java: 13
file content (14 lines) | stat: -rw-r--r-- 807 bytes parent folder | download | duplicates (3)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
For multi-homed computers, including gateway machines on a cluster, the network
address of the machine is not unique.  The coordinator will determine its
default hostname using 'hostname()', which will normally have been configured
to specify the hostname within a cluster.  The hostname is then used to
determine the ip address using getaddrinfo(). Any compute nodes will ask the
coordinator what address the coordinator sees when talking with the compute
node.  This will be taken as the address of the compute node within the DMTCP
computation.

In some rare cases, it is possible the getaddrinfo returns the loopback address
(127.0.0.1) instead of the real-ip address.  In such cases, one could use one
of host/dig/gethostent to guess the correct address.  This scheme is not yet
implemented in DMTCP.