mirror of
https://github.com/gnustep/libs-base.git
synced 2025-04-22 16:33:29 +00:00
Improve documentation
git-svn-id: svn+ssh://svn.gna.org/svn/gnustep/libs/base/trunk@30651 72102866-910b-0410-8b05-ffd578937521
This commit is contained in:
parent
5289d04e3f
commit
f9d435aa2a
2 changed files with 37 additions and 3 deletions
|
@ -42,8 +42,8 @@ gdomap \- GNUstep Distributed Objects name server
|
|||
The gdomap daemon is used by GNUstep programs to look up distributed objects of
|
||||
processes running on the local machine as well as across the network. This
|
||||
manual page explains the usage of gdomap. For design and implementation
|
||||
information, please see the HTML documentation installed in
|
||||
$GNUSTEP_SYSTEM_DOC, under Command-line Tools.
|
||||
information (nad special notes for packagers), please see the HTML
|
||||
documentation installed in $GNUSTEP_SYSTEM_DOC, under Command-line Tools.
|
||||
.P
|
||||
Usually the gdomap daemon is started at system boot time and binds itself to
|
||||
port 538. See the
|
||||
|
@ -51,7 +51,7 @@ port 538. See the
|
|||
for a sample startup script.
|
||||
|
||||
.P
|
||||
Gdomap normally probes every machine on the local network to see if there
|
||||
By default gdomap probes every machine on the local network to see if there
|
||||
is a copy of gdomap running on it. This is done for class-C networks and
|
||||
subnets of class-C networks. If your host is on a class-B or class-A net
|
||||
then the default behaviour is to treat it as a class-C net and probe only
|
||||
|
|
|
@ -24,6 +24,10 @@ notice and this notice are preserved.
|
|||
objects of processes running on the local machine as well as across
|
||||
the network.
|
||||
</p>
|
||||
<p>
|
||||
If you are packaging GNUstep for inclusion in a software distribution
|
||||
you may want to skip to the final section of this document.
|
||||
</p>
|
||||
<p>
|
||||
Usually the gdomap daemon is started at system boot time and binds
|
||||
itself to port 538. (See the GNUstep Build Guide for a sample
|
||||
|
@ -309,6 +313,36 @@ notice and this notice are preserved.
|
|||
</deflist>
|
||||
</section>
|
||||
|
||||
<section>
|
||||
<heading>Notes for Packagers</heading>
|
||||
|
||||
<p>
|
||||
The gdomap process is a system daemon used to coordinate
|
||||
services between different machines. As such it should be
|
||||
started (as root) at system boot time (if inter-host messaging
|
||||
is desired), and you need to write the appropriate startup
|
||||
scripts for your system and put them in place when the
|
||||
package is installed.<br />
|
||||
Alternatively you may install gdomap setuid to run as root,
|
||||
and GNUstep programs will launch it on demand ... but this
|
||||
is not recommended as it provides lass control than when
|
||||
you write a proper startup script.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
The default operation of gdomap is to probe the hosts on the
|
||||
local network to find other machines with copies of gdomap
|
||||
running, so that all the machines on the network can be kept
|
||||
informed of the seervices provided by GNUstep servers.<br />
|
||||
This probing may be considered unfriendly by other users of
|
||||
the LAN, so it is usually better to provide a configuration
|
||||
file specifying the IP addresses of machines to be probed,
|
||||
and start up gdomap at boot time with the command line option
|
||||
to tell it to read the file.
|
||||
</p>
|
||||
|
||||
</section>
|
||||
|
||||
</chapter>
|
||||
</body>
|
||||
</gsdoc>
|
||||
|
|
Loading…
Reference in a new issue