nns(1)

💖 nns — Name service facility, Commandline Client Application 💖

okay bestie, welcome to the nns(1) manual page 🎀 it's a section 1 page, it lives in tcllib, and it's literally the glow-up your name service needed. sit down, grab a strawberry drink 🍓, we're doing this.

---

✨ NAME ✨

nns — Name service facility, Commandline Client Application 👑

---

🌸 SYNOPSIS 🌸

nns bind ?-host host? ?-port port? name data

nns search ?-host host? ?-port port? ?-continuous? ?pattern?

nns ident ?-host host? ?-port port?

nns who

---

🦋 DESCRIPTION 🦋

first things first, babe: go read Name service facility, introduction before you touch any of this. it's giving required reading, i don't make the rules 💅

so. the app this doc is about, nns, is a simple command line client for the nano name service facility that comes from the Tcllib packages nameserv and nameserv::server. and not only that — the application's sources also serve as a whole example of how to use the client package nameserv. like, every single ability a client has is covered in there: from configuration, to registration of names, to searching. all of it. no crumbs left. 🔥

⚠️ important psa: this name service facility has nothing to do with the Internet's Domain Name System, aka DNS. like, zero. not the same thing, not related, don't @ me. if you are looking for a package that deals with that, please see either of the packages dns and resolv — both of which are found in Tcllib too. 🫶

👑 USE CASES 👑

nns was written with these two main use cases in mind, periodt:

1. Registration of a name/data pair in the name service. 📝
2. Searching the name service for entries matching a glob pattern. 🔍

and beyond the above? we also wanna be able to identify the client, and get information about the name service. main character energy all around ✨

💻 COMMAND LINE 💻

• nns bind ?-host host? ?-port port? name data — this form registers the name/data pair in the specified name service. and here's the thing: in this form the command will not exit, because it has to keep the registration alive. so you have to kill it explicitly — either by sending a signal, or through the job-control facilities of whatever shell you're using. and it will especially survive the loss of the connection to the name service, and reestablish the name/data pair when the connection is restored. resilient queen 💪

the options to specify the name service get explained later, in the section OPTIONS.

• nns search ?-host host? ?-port port? ?-continuous? ?pattern? — this form searches the specified name service for entries matching the glob-pattern and prints them to stdout, with each entry on its own line. if no pattern is specified it defaults to *, matching everything. (so generous of it 🥰)

the options to specify the name service get explained later, in the section OPTIONS.

if the option -continuous is specified, the client will not exit after performing the search — instead it starts to continuously monitor the service for changes to the set of matching entries, appropriately updating the display as changes arrive. and in that form it will especially also survive the loss of the connection to the name service, and reestablish the search when the connection is restored. it's committed, it's loyal, it's everything 😭

• nns ident ?-host host? ?-port port? — this form asks the specified name service for the version and features of the name service protocol it supports, and prints the results to stdout. it's basically asking the service "who are you and what can you do" and the service answers. iconic. 🎀

the options to specify the name service get explained later, in the section OPTIONS.

• nns who — this form prints name, version, and protocol version of the application to stdout. it's the app's little "hi, this is me" moment 💅

---

✨ OPTIONS ✨

this section describes all the options available to the user of the application. all of them. we don't gatekeep here.

• -host name|ipaddress — 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. 🏠
• -port number — 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. 📮

---

🫶 BUGS, IDEAS, FEEDBACK 🫶

ngl, this document, and the package it describes, will undoubtedly contain bugs and other problems. it's fine, we're all growing 🌱 please report such in the category nameserv of the Tcllib Trackers [http://core.tcl.tk/tcllib/reportlist]. and please also report any ideas for enhancements you may have for either package and/or documentation — we want the ideas, we love the ideas 💜

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. do it that way bestie, trust 🤞

---

🌈 SEE ALSO 🌈

• nameserv(3tcl)
• nameserv::common(3tcl)

---

🎀 KEYWORDS 🎀

application, client, name service

---

💅 CATEGORY 💅

Networking

---

💖 COPYRIGHT 💖

Copyright (c) 2007-2008 Andreas Kupries <andreas_kupries@users.sourceforge.net>

---

okay that's the whole page, you ate that 🍽️ this was tcllib 1.1, the nns(1) manual page, and you're officially caught up. go register some name/data pairs, bestie, and remember: not DNS. never DNS. bye babe 💖✨🦋