[ Main Table Of Contents | Table Of Contents | Keyword Index | Categories | Modules | Applications ]
nnslog - Name service facility, Commandline Logging Client Application
Please read Name service facility, introduction first.
It essentially implements "nns search -continuous *", but uses a different output formatting. Instead of continuously showing the current contents of the server in the terminal it simply logs all received add/remove events to stdout.
This name service facility has nothing to do with the Internet's Domain Name System, otherwise known as DNS. If the reader is looking for a package dealing with that please see either of the packages dns and resolv, both found in Tcllib too.
nnslog was written with the following main use case in mind.
- Monitoring the name service for all changes and logging them in a text terminal.
The command connects to the specified name service, sets up a search for all changes and then prints all received events to stdout, with each events on its own line. The command will not exit until it is explicitly terminated by the user. It will especially survive the loss of the connection to the name service and reestablish the search and log when the connection is restored.
The options to specify the name service will be explained later, in section OPTIONS.
This section describes all the options available to the user of the application
If this option is not specified it defaults to localhost. It specifies the name or ip-address of the host the name service to talk to is running on.
If this option is not specified it defaults to 38573. It specifies the TCP port the name service to talk to is listening on for requests.
This document, and the package it describes, will undoubtedly contain bugs and other problems. Please report such in the category nameserv of the Tcllib Trackers. Please also report any ideas for enhancements you may have for either package and/or documentation.
When proposing code changes, please provide unified diffs, i.e the output of diff -u.
Note further that attachments are strongly preferred over inlined patches. Attachments can be made by going to the Edit form of the ticket immediately after its creation, and then using the left-most button in the secondary navigation bar.
Copyright © 2008 Andreas Kupries