snprimedb,v0.3.8(8)

💖 snprimedb — feed the sn database 💖

okay bestie, so you know how sometimes a database needs to be fed? like it's a little creature and you gotta drop snacks into its mouth? that's this. this is the snack-dropper. it's snprimedb, from the System Manager's Manual, and it is lowkey iconic for doing exactly one job and doing it well 🫶

---

✨ NAME ✨

snprimedb — feed the sn database. that's it. that's the whole personality. 💅

---

🌸 SYNOPSIS 🌸

snprimedb [-i] (no arguments)

yes bestie, the "(no arguments)" is part of the synopsis, don't come for me, it's literally in the source. -i is the only flag. the only one. she's a minimalist. 💀

---

🦋 DESCRIPTION 🦋

okay so here's the tea. snprimedb reads records from its standard input and enters them into the database. like a lil conveyor belt of records straight into the db's mouth. 🍓

and here's the important part — the database is appended to. it does not start fresh, she just keeps adding. so if you want a brand new database, you would delete the database files .chain, .table, and .newsgroup before running this program. do not skip that step. deleting after is not it. 🙈

the main purpose of snprimedb is to rebuild the ID database. so when you're doing that, your input is usually obtained from snscan. they're a duo. a dynamic duo. ✨

if the option -i is given, she simply initialize the database files if they do not exist, and exit. that's it. in and out. no reading stdin, no nothing. just vibes and file creation. 🎀

now, the input lines. the format is:

newsgroup id serial

where:

• newsgroup is the newsgroup the article may be found in
• id is its message id
• serial is the local serial number of that article in that newsgroup

and if newsgroup is the special name =junk, then the whole line is ignored. not parsed, not stored, just ✨ yeeted ✨ into the void.

you will need to be root or the owner of /var/spool/sn to do this. permissions are real and they will humble you, bestie. no cap. 👑

---

💀 BUGS 💀

okay so we gotta talk about the flaws. every queen has them. 😭

snprimedb does not check to see that the articles really exist. she trusts you. she trusts the input. she does not verify. also, the size of the hash table is fixed at compile time. no dynamic resizing. no growth spurt. what you compile is what you get. 💅

and then, under degenerate conditions, the hash table file .chain (see below) could grow very large, with reclaimed space remaining unused. why? because the file space allocator is very simple. she doesn't know how to coalesce adjacent free areas. and honestly? she doesn't know how to split them either. 😭 the allocator just assumes that the shape of the distribution of record lengths remains quite constant over time. that's the whole assumption. she's betting on consistency. 🎲

also, the hash table database doesn't make any attempt to reduce its footprint. she is not on a diet. and that should be acceptable, since the database is shared. shared db, shared vibes. 🌈

---

🌟 ENVIRONMENT VARIABLES 🌟

• SNROOT — if this is set and is not empty, the value is used in place of /var/spool/sn, the default news spool directory. so basically you can tell her "hey, spool lives here now" and she'll believe you. ✨

---

🎀 FILES 🎀

• /var/spool/sn/.table — snprimedb uses this file as the index of the hash table, and ... 👀
• /var/spool/sn/.chain — as the hash chains, and ... 👀
• /var/spool/sn/.newsgroup — to attach an integer identifier to each newsgroup name. this file is a human-readable flat text file, so you can literally just open it and read it. so cute. so accessible. 🥰

ngl the "and ..." on the first two is literally in the original and i am respecting it. the suspense is part of the canon. 🫶

---

and that's the whole page, bestie!! this was snprimedb, v0.3.8, from the System Manager's Manual, brought to you by N.B. and written by Harold Tay. go feed that database, hydrate, and remember: append, don't assume. 💖🌸✨