---
name: "nws_nameserver"
section: "1"
platform: "linux"
package: "nws"
version: "2.13-6.1"
release: "Debian 5.0 (Lenny)"
platforms: ["linux"]
url: "https://new.carta.tech/nws_nameserver"
---

# nws\_nameserver(1)

nameserver for the Network Weather Service

## NAME

nws\_nameserver - nameserver for the Network Weather Service

## SYNOPSIS

**nws\_nameserver** \[-a addresses\]\[-n name\]\[-D\]\[-e file\]\[-l file\]\[-i file\]\[-m\]\[-N nameserver\]\[-f file\]\[-p port\]

## DESCRIPTION

This manual page explains the  **nws\_nameserver** program. Other NWS hosts ( **[nws\_sensor(1)](/nws_sensor/1.md),**[nws\_memory(1)](/nws_memory/1.md) ) register their locations and attributes with a **nws\_nameserver.** We recommend that NWS users run their own **nws\_nameserver.**

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  *name* attribute that identifies the object (this attribute should be unique) and an  *objectclass* attribute that specifies what sort of item the object represents.

Here are some of the attributes you can find (see **[nws\_search(1)](/nws_search/1.md)** on how to query a  **nws\_namserver.** Typically objects have some of the following attributes (in addition to name and objectclass):

**timestamp**

is the expiration time of the object: it won't show up past this time, unless the object is re-registered.

**host**

machine which hosts the daemons in name:port format

**memory**

nws\_memory which holds the measurements related to this object

**hostType**

kind of NWS process (for example nws\_nameserver, nws\_memory or sensor)

**ipAddress**

list of IP addresses associated with this host that are available to NWS

**owner**

login of the person who started this NWS host

**port**

port which the host is listening to

## OPTIONS

- **-a** *addresses*

  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.

- **-n** *name*

  Use  *name* as hostname. Useful the resolver aren't correctly configured and  gethostname doesn't return a resonable value.

- **-e** *file*

  Save the error messages to  *file.*

- **-l** *file*

  Save the log messages to  *file.*

- **-i** *file*

  Write the pid to  *file*

- **-m**

  Enable mirroring code: if we got a nameserver in our registration we try to sync with it and keep our registration synchronized. See -N.

- **-N** *nameserver*

  Try to read all the registrations from  *nameserver* and add to our pool of registrations. If used with -m try to keep the nameservers in sync.

- **-f** *file*

  Save the registrations to  *file.* Remember that  *file* whenever a new version of registration is written. The deafult filename is  *registrations.*

**-p** *port* Listen to port instead of the default for the nws\_nameserver (8090).

## BUGS

This man page doesn't explain all the possible options that the nws\_nameserver will obey.

Bugs list is at  http://nws.cs.ucsb.edu. ⟨http://nws.cs.ucsb.edu⟩

## AUTHOR

NWS is an original idea of Rich Wolski (rich@cs.ucsb.edu). The  **nws\_nameserver** is been introduced by Jim Hayes (jhayes@cs.ucsd.edu) and is been almost entirely rewritten by Graziano Obertelli (graziano@cs.ucsb.edu) who currently maintains NWS.

This man page is been written by Graziano Obertelli (graziano@cs.ucsb.edu).

## SEE ALSO

**[nws\_sensor(1)](/nws_sensor/1.md),** **[nws\_search(1)](/nws_search/1.md),** **[nws\_memory(1)](/nws_memory/1.md),** **[nws\_extract(1)](/nws_extract/1.md)** **halt\_activity(1)** **start\_activity(1)**