TTDBSERVERD(1m)

💅 ttdbserverd — the RPC-based ToolTalk database server (yes that's the real name, it's from user cmd, iykyk)

okay so bestie, buckle up, because we're talking about ttdbserverd, aka rpc.ttdbserverd when it's being fancy in the synopsis. it's the RPC-based ToolTalk database server and honestly it's doing SO much behind the scenes. ✨

---

🌸 SYNOPSIS 🌸

rpc.ttdbserverd [-G] [-m DTMOUNTPOINT_value] [-n] [-v] [-?]

look at her. five little flags. icon behavior. 🎀

---

💖 DESCRIPTION 💖

okay so here's the tea: rpc.ttdbserverd manages the ToolTalk objects that get created by tt_spec_create(3), and it also handles certain queries related to the netfiles that tt_file_netfile(3) hands back. one instance of rpc.ttdbserverd — normally started by inetd, no cap — runs on each host that has a local filesystem. literally one per host with a local fs, that's the rule. 🫶

and it serves four purposes, bestie, four whole jobs:

1. mapping a spec to its associated file, and a file to its associated specs.
2. mapping a spec to its properties.
3. mapping a file to a list of sessions with clients having patterns registered in the scope of that file.
4. answering netfile queries — see tt_file_netfile(3) and tt_host_file_netfile(3).

now, the storage situation 📁 — for each filesystem that rpc.ttdbserverd needs to store information about, it creates a directory called TT_DB at the mountpoint of that file system. in that directory it creates the databases it needs to store its tables and indices. slay.

but what if the partition isn't writable? 💀 then rpc.ttdbserverd can be told, via partition_map(4), to create the databases in another local partition. and if rpc.ttdbserverd isn't installed on a particular file server, ToolTalk can be told, via hostname_map(4), to manage that file server's partitions using the rpc.ttdbserverd on a different host. teamwork makes the dream work fr fr. 🌈

---

✨ OPTIONS ✨

• -G — perform garbage collection 🗑️. this cleans up the TT_DB directories and the associated internal database files. self-care for your db, honestly.
• -m DTMOUNTPOINT_value — sets the DTMOUNTPOINT environment variable for rpc.ttdbserverd. and if there's already an environment variable called DTMOUNTPOINT? yeah, -m will override it. take that, existing env var. 💅
• -n — turn off permission checking 🙈. normally the protection of the file passed to tt_spec_create(3) determines who may read and write that spec. this option disables this checking and allows anyone to read and write any spec. so basically everyone gets the aux cord. no big deal. except it IS a big deal.

bestie, listen to me: this option should be used with caution. that's not me being dramatic, that's the manpage. 🔥

• -v — print out the version number. cute, quick, slay. ⭐
• -? — prints out the command usage information. the "help, what do I type" button. 👑
• -? — (yes, again, that's what's in the page — see below 💀)

wait no, literally just the five above: -G, -m, -n, -v, -?. that's the whole lineup. 🦋

---

🧚 ENVIRONMENT 🧚

• DTMOUNTPOINT — if set, the value of this environment variable will be used in place of /net in pathnames constructed to answer tt_host_netfile_file(3) queries. this environment variable can also be set by using the -m flag for rpc.ttdbserverd. ✨
• TT_PARTITION_MAP — if set, the value of this environment variable will be used in place of /etc/tt/partition_map. see partition_map(4). 📌

---

🍓 FILES 🍓

• TT_DB/* — spec and session database files are kept in the TT_DB directory under each disk partition mount point. 🗂️
• tt/hostname_map — host redirection map. see hostname_map(4).
• /etc/tt/partition_map — partition redirection map. see partition_map(4).

---

🔥 SEE ALSO 🔥

ttsession(1), tt_file_netfile(3), tt_host_file_netfile(3), tt_spec_create(3), hostname_map(4), partition_map(4)

go read them, bestie, they're all connected and the lore runs deep. 💜

---

🎀 sign-off 🎀

and that's the whole page, no notes! this one's filed under ttdbserverd(user cmd) — that's the manual name up there at the top and the footer label down here at the bottom, so now you know where to find her again. no version number or date was given in the original, so we're not making one up. periodt. 🌸

now go make sure your TT_DB directories are cute and your permission checking is ON. mwah. 💖