nnsd(n)

πŸ’– nnsd(n) β€” the name service facility's commandline server app πŸ’–

okay so bestie, you're holding the manual for nnsd(n), aka the Name service facility, Commandline Server Application. yes that's the whole vibe. let's get into it 🫢


✨ SYNOPSIS ✨

nnsd ?-localonly flag? ?-port port?

that's it. that's the whole synopsis. short and iconic πŸ’…


🌸 DESCRIPTION 🌸

okay first thing first: please go read Name service facility, introduction before this. like actually. it's the prerequisite bestie, don't skip it πŸ™ˆ

so. the application this doc is describing, nns, is a simple command line server for the nano name service facility that comes from the Tcllib packages nameserv and nameserv::server. and lowkey the cutest part? the application's own sources double as an example of how you're supposed to use the server package nameserv::server. so it's both a program AND a tutorial. main character energy fr fr ✨

⚠️ okay important: this name service facility has nothing to do with the Internet's Domain Name System, aka DNS. like zero relation, no cap. if that's the thing you're actually looking for, go check out the packages dns and resolv instead β€” both of them also live in Tcllib πŸ’œ

πŸ¦‹ USE CASES πŸ¦‹

nnsd was written with one main use case in mind, and here it is:

  1. Run a nano name service on some host.

that's the list. one item. focused queen πŸ‘‘

πŸŽ€ COMMAND LINE πŸŽ€

nnsd ?-localonly flag? ?-port port?

so this command configures a server according to whatever options you passed, and then it starts it. and then… it just. keeps going. it will not exit on its own, because it's holding the whole name service database wholly in memory the entire time. so the user β€” that's you, bestie β€” has to kill it explicitly. you've got two ways:

  • sending it a signal πŸ“‘
  • using the job-control facilities of the shell you're in 🐚

the options for configuring the name service are all explained down in the OPTIONS section. keep scrolling πŸ’…


✨ OPTIONS ✨

this section describes all the options available to you, the user of the application. there are two. they're both here. no gatekeeping 🫢

  • -localonly bool β€” if you don't specify this one, it defaults to true, which means it only accepts local connections. the server will accept remote connections β€” like, connections coming in from other hosts β€” if and only if this option is set to false. so flip it to false only if you actually mean it, okay? πŸ”₯
  • -port number β€” if you don't specify this one, it defaults to 38573. it sets the TCP port the server has to listen on for requests. that's the number, that's the port, that's the whole job πŸ’…

😭 BUGS, IDEAS, FEEDBACK 😭

ngl, this document and the package it describes will undoubtedly contain bugs and other problems. like, they said it themselves. so please report those in the category nameserv of the Tcllib Trackers at http://core.tcl.tk/tcllib/reportlist. and if you have any ideas for enhancements for either the package and/or the documentation? report those too, they wanna hear it 🫢

if you're proposing code changes, please bring unified diffs β€” that means the output of diff -u. that's the format, that's the assignment πŸ“

πŸ’€ also, heads up: attachments are strongly preferred over inlined patches. so don't paste your patch in the middle of the ticket like it's a group chat message. to attach something, go to the Edit form of the ticket right after you create it, and then use the left-most button in the secondary navigation bar. iykyk ✨

🌈 SEE ALSO 🌈

  • nameserv::common(n)
  • nameserv::server(n)

go read those too, they're the lore πŸ‘‘


⭐ 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, you ate it πŸ’… this was tcllib version 1.0.1, and yeah that's the whole nnsd(n) situation. now go run your nano name service, slay, and remember to kill it yourself because it will NOT do it for you πŸ˜­πŸ’–πŸ¦‹

πŸ“¦ where this page comes from