This manual page explains the
program. Other NWS hosts (
) register their locations and attributes with a
We recommend that NWS users run their own
NWS registrations follow the LDAP model. Each registered object consists
of a set of attributes that are described by name-value pairs. Every
object has a
attribute that identifies the object (this attribute should be unique)
attribute that specifies what sort of item the object represents.
Here are some of the attributes you can find (see
on how to query a
Typically objects have some of the following attributes (in addition to
name and objectclass):
is the expiration time of the object: it won't show up past this time,
unless the object is re-registered.
machine which hosts the daemons in name:port format
nws_memory which holds the measurements related to this object
kind of NWS process (for example nws_nameserver, nws_memory or sensor)
list of IP addresses associated with this host that are available to NWS
login of the person who started this NWS host
port which the host is listening to
Specified a comma separated list of addresses (IPs or name) that the
sensor will consider be aliases for the localhost. Used for multihomed
machine when DNS doesn't return all the IPs associated with a name.
as hostname. Useful the resolver aren't correctly configured and
gethostname doesn't return a resonable value.
Save the error messages to
Save the log messages to
Write the pid to
Enable mirroring code: if we got a nameserver in our registration we try
to sync with it and keep our registration synchronized. See -N.
Try to read all the registrations from
and add to our pool of registrations. If used with -m try to keep the
nameservers in sync.
Save the registrations to
whenever a new version of registration is written. The deafult filename is
Listen to port instead of the default for the nws_nameserver (8090).
This man page doesn't explain all the possible options that the
nws_nameserver will obey.