nnslog(n)

📦 version 2.0, in alpine 3.24, epel 9, fedora 43, fedora 44, nixos 26.05, nixpkgs unstable, opensuse-leap 16.0

💖 nnslog(n) — Name service facility 💖

okay bestie so this is the manual page for nnslog, aka the Name service facility, Commandline Logging Client Application. yeah that's a lot of capital letters, i know, but it's literally just a lil logging buddy. let's go 🫶

✨ SYNOPSIS ✨

nnslog ?-host host? ?-port port?

🌸 DESCRIPTION 🌸

first things first, bestie: go read Name service facility, introduction. like, actually. it's the prerequisite, no skipping 🙈

so. the app this page is about, nnslog, is a simple command line client for the nano name service facility — the one provided by the Tcllib packages nameserv and nameserv::server. cute, right?

basically it does the same thing as nns search -continuous *, but the output formatting is different. instead of continuously showing you the current contents of the server all up in your terminal, it just logs every single add/remove event it receives to stdout. stream of events, one after another. it's giving live feed energy 💅

⚠️ ok important: this name service facility has nothing to do with the Internet's Domain Name System, aka DNS. like, zero. different thing entirely. if that's what you came here for, go look at the packages dns and resolv instead — both also live in Tcllib. no cap 🧚

🦋 USE CASES 🦋

nnslog was written with this main use case in mind:

  1. Monitoring the name service for all changes and logging them in a text terminal.

that's it, that's the whole list. it does one thing and it slays at it ✨

🌈 COMMAND LINE 🌈

nnslog ?-host host? ?-port port?

the command connects to the name service you specified, sets up a search for all changes, and then prints every received event to stdout — each event on its own line, bestie, we're tidy here 💅

it will not exit until you explicitly terminate it. it is not leaving. it lives here now 👑

and the iconic part? it will especially survive the loss of the connection to the name service, and it reestablishes the search and the log once the connection is restored. resilient queen 🎀

the options for specifying the name service get explained later, down in OPTIONS. patience, babes 😌

💜 OPTIONS 💜

this section describes all the options available to you, the user of the application. there are two. two options. love that for us.

  • -host name|ipaddress — if you don't specify this one it defaults to localhost. it specifies the name or ip-address of the host that the name service you wanna talk to is running on. 🏠
  • -port number — if you don't specify this one it defaults to 38573. it specifies the TCP port that the name service you wanna 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. like, it's software, bestie. please report them 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 the package and/or the documentation — we wanna hear it, fr fr 🫶

when proposing code changes, please provide unified diffs, i.e. the output of diff -u.

also note further that attachments are strongly preferred over inlined patches. you can make attachments 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. iykyk 💅

👀 SEE ALSO 👀

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

⭐ KEYWORDS ⭐

application, client, name service

🎀 CATEGORY 🎀

Networking

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

and that's the whole page, bestie!! this was tcllib version 1.0 doing its thing, and honestly? iconic behavior. go log some events, you main character 💅✨🦋

📦 where this page comes from