1GDOMAP(8) GNUstep System Manual GDOMAP(8)
2
3
4
6 gdomap - GNUstep Distributed Objects name server
7
8
10 gdomap [-C|-H] [-I pidfile] [-L name] [-M name] [-N] [-P number] [-R
11 name] [-S] [-T type] [-U name] [-a file] [-c file] [-d] [-f] [-i sec‐
12 onds] [-j path] [-p]
13
14
16 gdomap The gdomap daemon is used by GNUstep programs to look up dis‐
17 tributed objects of processes running across the network (and between
18 different user accounts on a single machine). The daemon is NOT used
19 for lookup where two processes belonging to the same user are using a
20 host-local connection. This manual page explains the usage of gdomap.
21 For design and implementation information (and special notes for pack‐
22 agers), please see the HTML documentation installed in $GNUSTEP_SYS‐
23 TEM_DOC, under Command-line Tools.
24
25 Usually the gdomap daemon is started at system boot time and binds
26 itself to port 538. See the GNUstep Build Guide for a sample startup
27 script.
28
29
30 By default gdomap probes every machine on the local network to see if
31 there is a copy of gdomap running on it. This is done for class-C net‐
32 works and subnets of class-C networks. If your host is on a class-B or
33 class-A net then the default behaviour is to treat it as a class-C net
34 and probe only the hosts that would be expected on a class-C network of
35 the same number.
36
37 If you are running on a class-A or class-B network, or if your net has
38 a large number of hosts which will not have gdomap on them - you may
39 want to supply a configuration file listing the hosts to be probed
40 explicitly, rather than getting gdomap to probe all hosts on the local
41 net.
42
43 You may also want to supply the configuration file so that hosts which
44 are not actually on your local network can still be found when your
45 code tries to connect to a host using @"*" as the host name. NB. this
46 functionality does not exist in OpenStep.
47
48 A configuration file consists of a list of IP addresses to be probed.
49 The IP addresses should be in standard 'dot' notation, one per line.
50 Empty lines are permitted in the configuration file. Anything on a
51 line after a hash ('#') is ignored. You tell gdomap about the config
52 file with the '-c' command line option.
53
54 gdomap uses the SIOCGIFCONF ioctl to build a list of IP addresses and
55 netmasks for the network interface cards on your machine. On some
56 operating systems, this facility is not available (or is broken), so
57 you must tell gdomap the addresses and masks of the interfaces using
58 the '-a' command line option. The file named with '-a' should contain
59 a series of lines with space separated pairs of addresses and masks in
60 'dot' notation. You must NOT include loopback interfaces in this list.
61 If you want to support broadcasting of probe information on a network,
62 you may supply the broadcast address as a third item on the line. If
63 your operating system has some other method of giving you a list of
64 network interfaces and masks, please send me example code so that I can
65 implement it in gdomap.
66
67
69 -C help about configuration
70
71 -H general help
72
73 -I pid file to write pid
74
75 -L name
76 perform lookup for name then quit.
77
78 -M name
79 machine name for -L and -N
80
81 -N list all names registered on host
82
83 -P number
84 port number required for -R option.
85
86 -R name
87 register name locally then quit. -S
88
89 -S list the addresses of all gdomap servers known to host
90
91 -T type
92 port type for -L , -R and -U options - tcp_gdo, udp_gdo,
93 tcp_foreign, udp_foreign.
94
95 -U name
96 unregister name locally then quit.
97
98 -a file
99 use config file for interface list.
100
101 -c file
102 use config file for probe.
103
104 -d extra debug logging (normally via syslog).
105
106 -f avoid fork() to make debugging easy
107
108 -i seconds
109 re-probe at this interval (roughly), min 60
110
111 -j path
112 place the process in a chroot jail at this path rather than in
113 /tmp
114
115 -p disable probing for other servers
116
118 Use the -c option to specify a configuration file for gdomap. See under
119 DESCRIPTION for possible configurations.
120
121
123 Kill with SIGUSR1 to obtain a dump of all known peers in
124 /tmp/gdomap.dump
125
126 gdomap -N lists all registered names on the local host.
127
128
130 gdomap -C gives above instructions on how to set up gdomap.
131
132 gdnc(1), GNUstep(7), gpbs(1)
133
134 The GNUstep Build Guide example rc script: <http://gnustep.made-
135 it.com/BuildGuide/index.html#GNUSTEP.SERVICES>
136
138 Work on gdomap started in October 1996.
139
140 This manual page first appeared in gnustep-base 1.7.1 (June 2003).
141
143 gdomap was written by Richard Frith-Macdonald <rfm@gnu.org>
144
145 This manual page was put together by Martin Brecher <martin@mb-itcon‐
146 sulting.com>.
147
148
149
150GNUstep August 2003 GDOMAP(8)