OVSQLITE-SERVER(8)

✨ OVSQLITE-SERVER(8) ✨

okay so this is a page from the InterNetNews Documentation bestie, and it's literally about ovsqlite-server — the one and only queen of the ovsqlite database 👑

---

💖 NAME 💖

ovsqlite-server — the sole owner of the ovsqlite database. like, nobody else gets keys to that house. periodt 🔑

---

🎀 SYNOPSIS 🎀

ovsqlite-server [-d]

---

🦋 DESCRIPTION 🦋

So the ovsqlite-server daemon is the only program that opens the overview SQLite database. That's it. That's the whole vibe. It's giving main character energy with a strict "no guests" policy 💅

It accepts connections from the other parts of INN that wanna operate on overview data — and those are:

• innd
• nnrpd
• expireover
• makehistory

Because of this, the daemon must be started before any other process can access the overview database. No cap, if it's not up, nobody's getting in 🙈

ovsqlite-server is normally invoked automatically by rc.news when starting the news system. It also gets stopped automatically by rc.news when stopping the news system. so it's got a whole entourage handling its schedule, iconic behavior honestly 🌸

Now — in case you need to talk to this daemon from Perl, the binary protocol used to communicate with it has been implemented in the INN::ovsqlite_client Perl module. See its manual page for more info about its possibilities 🫶

---

✨ OPTIONS ✨

• -d — normally ovsqlite-server puts itself into the background, points its standard output and error to log files, and disassociates itself from the terminal. Using -d prevents all of this, resulting in log messages being written to the standard error output. this is generally useful only for debugging 🐛 (lowkey the vibes-only mode)

---

🌈 FILES 🌈

• pathetc/ovsqlite.conf — the configuration file. See ovsqlite(5) 📝
• pathoverview/ovsqlite.db — the SQLite database file 💾
• pathrun/ovsqlite.pid — stores the PID of the server process while it's running 🆔
• pathrun/ovsqlite.sock — when Unix-domain sockets are available, the server binds its listening socket to this path 🔌
• pathrun/ovsqlite.port — when Unix-domain sockets aren't available, the server binds its listening socket to a dynamic TCP port on the IPv4 loopback interface and stores the port number in this file 🌐

---

💜 HISTORY 💜

Initial implementation of ovsqlite written by Bo Lindbergh <2bfjdsla52kztwejndzdstsxl9athp@gmail.com> for InterNetNews. we love a founder moment 👑✨

---

🍓 SEE ALSO 🍓

INN::ovsqlite_client(3pm), ovsqlite(5), rc.news(8). iykyk, go read those next bestie 📚

---

ngl this is the whole page, so go forth and let the daemon own its database in peace 💖

okay that's the tea — this was INN 2.7.4, dated 2024-05-19, brought to you by your favorite OVSQLITE-SERVER(8) manual page 🧚‍♀️💫