gdomap(8)

1GDOMAP(8)                    GNUstep System Manual                   GDOMAP(8)
2
3
4

NAME

6       gdomap - GNUstep Distributed Objects name server
7
8

SYNOPSIS

10       gdomap  [-C|-H]  [-I  pidfile] [-L name] [-M name] [-N] [-P number] [-R
11       name] [-T type] [-U name] [-a file] [-c file] [-d]  [-f]  [-i  seconds]
12       [-p]
13
14

DESCRIPTION

16       gdomap  The  gdomap  daemon is used by GNUstep programs to look up dis‐
17       tributed objects of processes running on the local machine as  well  as
18       across  the  network.   This  manual page explains the usage of gdomap.
19       For design and implementation information (nad special notes for  pack‐
20       agers),  please  see  the HTML documentation installed in $GNUSTEP_SYS‐
21       TEM_DOC, under Command-line Tools.
22
23       Usually the gdomap daemon is started at  system  boot  time  and  binds
24       itself  to  port  538. See the GNUstep Build Guide for a sample startup
25       script.
26
27
28       By default gdomap probes every machine on the local network to  see  if
29       there is a copy of gdomap running on it.  This is done for class-C net‐
30       works and subnets of class-C networks.  If your host is on a class-B or
31       class-A  net then the default behaviour is to treat it as a class-C net
32       and probe only the hosts that would be expected on a class-C network of
33       the same number.
34
35       If  you are running on a class-A or class-B network, or if your net has
36       a large number of hosts which will not have gdomap on them  -  you  may
37       want  to  supply  a  configuration  file listing the hosts to be probed
38       explicitly, rather than getting gdomap to probe all hosts on the  local
39       net.
40
41       You  may also want to supply the configuration file so that hosts which
42       are not actually on your local network can still  be  found  when  your
43       code  tries to connect to a host using @"*" as the host name.  NB. this
44       functionality does not exist in OpenStep.
45
46       A configuration file consists of a list of IP addresses to  be  probed.
47       The  IP  addresses  should be in standard 'dot' notation, one per line.
48       Empty lines are permitted in the configuration  file.   Anything  on  a
49       line  after  a hash ('#') is ignored.  You tell gdomap about the config
50       file with the '-c' command line option.
51
52       gdomap uses the SIOCGIFCONF ioctl to build a list of IP  addresses  and
53       netmasks  for  the  network  interface  cards on your machine.  On some
54       operating systems, this facility is not available (or  is  broken),  so
55       you  must  tell  gdomap the addresses and masks of the interfaces using
56       the '-a' command line option.  The file named with '-a' should  contain
57       a  series of lines with space separated pairs of addresses and masks in
58       'dot' notation.  You must NOT include loopback interfaces in this list.
59       If  you want to support broadcasting of probe information on a network,
60       you may supply the broadcast address as a third item on the  line.   If
61       your  operating  system  has  some other method of giving you a list of
62       network interfaces and masks, please send me example code so that I can
63       implement it in gdomap.
64
65

OPTIONS

67       -C     help about configuration
68
69       -H     general help
70
71       -I     pid file to write pid
72
73       -L name
74              perform lookup for name then quit.
75
76       -M name
77              machine name for -L and -N
78
79       -N     list all names registered on host
80
81       -P number
82              port number required for -R option.
83
84       -R name
85              register name locally then quit.
86
87       -T type
88              port  type  for  -L  ,  -R  and  -U  options - tcp_gdo, udp_gdo,
89              tcp_foreign, udp_foreign.
90
91       -U name
92              unregister name locally then quit.
93
94       -a file
95              use config file for interface list.
96
97       -c file
98              use config file for probe.
99
100       -d     extra debug logging (normally via syslog).
101
102       -f     avoid fork() to make debugging easy
103
104       -i seconds
105              re-probe at this interval (roughly), min 60
106
107       -p     disable probing for other servers
108

FILES

110       Use the -c option to specify a configuration file for gdomap. See under
111       DESCRIPTION for possible configurations.
112
113

DIAGNOSTICS

115       Kill   with   SIGUSR1   to   obtain  a  dump  of  all  known  peers  in
116       /tmp/gdomap.dump
117
118       gdomap -N lists all registered names on the local host.
119
120

HISTORY

130       Work on gdomap started in October 1996.
131
132       This manual page first appeared in gnustep-base 1.7.1 (June 2003).
133

AUTHORS

135       gdomap was written by Richard Frith-McDonald <rfm@gnu.org>
136
137       This  manual  page was put together by Martin Brecher <martin@mb-itcon‐
138       sulting.com>.
139
140
141
142GNUstep                           August 2003                        GDOMAP(8)