nnsd(1)

📦 version 2.0, in debian bookworm, debian trixie, ubuntu jammy, ubuntu noble, ubuntu questing, ubuntu resolute, ubuntu stonking

✨ nnsd — the manual page, but make it make sense 💅

okay so bestie, you opened nnsd(1) and that's the name service facility's commandline server application. that's the whole vibe. let's get into it 🫶

🌸 SYNOPSIS ✨

nnsd ?-localonly flag? ?-port port?

that's it. that's the whole thing. iconic honestly.

💖 DESCRIPTION 🌈

first things first: go read Name service facility, introduction before you do anything else. like, seriously. it's the pre-req. i'm not gonna let you skip it. 📚

so, the app this doc is about — nns — is a simple command line server for the nano name service facility, which comes from the Tcllib packages nameserv and nameserv::server. and lowkey the best part: the application's own source code doubles as a living example of how you're supposed to use the nameserv::server package. so if you're like "how do i even" — read the source, bestie. it's giving tutorial. 👑

⚠️ real talk though: this name service facility has absolutely nothing to do with the Internet's Domain Name System, aka DNS. zero. none. different species. if DNS is what you're actually after, go look at the packages dns and resolv — both also live in Tcllib. don't mix them up, i'm begging 🙈

🌟 USE CASES 🦋

nnsd was written with one main use case in mind:

  1. Run a nano name service on some host.

that's the list. one item. focused queen. 💅

🎀 COMMAND LINE ✨

nnsd ?-localonly flag? ?-port port?

this command sets up a server according to whatever options you gave it, then starts it. and then... it just keeps going. it will not exit on its own, because it holds the entire name service database wholly in memory. so you have to kill it yourself — either by sending a signal, or by using the job-control facilities of whatever shell you're in. no graceful little exit for you, sorry bestie 😭

all the options for configuring the name service are explained in the OPTIONS section, right down there 👇

🌈 OPTIONS ✨

this section covers every single option available to you:

  • -localonly bool — if you don't specify this, it defaults to true, which means only local connections get accepted. the server will accept remote connections — like, connections coming from other hosts — if and only if you set this option to false. so flip it and suddenly you're open to the world. no pressure. 🔥
  • -port number — if you don't specify this, it defaults to 38573. it sets the TCP port the server has to listen on for requests. that's the one. that's the number. 🍓

💀 BUGS, IDEAS, FEEDBACK 🫶

ngl, this document and the package it describes will undoubtedly contain bugs and other problems. it's just how it is. so please report them in the category nameserv of the Tcllib Trackers: [http://core.tcl.tk/tcllib/reportlist](http://core.tcl.tk/tcllib/reportlist). and while you're there, if you've got ideas for enhancements to the package and/or the documentation — send those too, we want them. 🌟

if you're proposing code changes, pls provide unified diffs — that's the output of diff -u. exactly that format. we're not doing guesswork here. ✨

also important: attachments are strongly preferred over inlined patches. to attach something, go to the Edit form of the ticket right after you create it, then hit the left-most button in the secondary navigation bar. that's the secret handshake. iykyk 🤫

👀 SEE ALSO 🦋

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

🏷️ KEYWORDS 💜

application, name service, server

🗂️ CATEGORY 🌸

Networking

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

and that's the whole page, bestie!! this was nnsd(1) from tcllib, version 1.0.1 🎀 go run your nano name service, stay local unless you mean it, and remember to actually kill the process. mwah 💅✨🫶

📦 where this page comes from