SQLite database : which file? about charybdis

[mvy]

The file is prefix/etc/ban.db. For some reason, +w is also required on the parent directory for the server to start correctly (at least the first time?)

[aaronmdjones]

Charybdis' bandb (specifically, the SQLite library), much like Atheme IRC Services, uses atomic database saving. This means it first creates a new file in the directory, and then moves it into place over the old one when it's completely written. Naturally, this requires +w on the directory. If this concerns you, you can also set +t on the directory:

# ls -ahl /usr/local/charybdis/etc/
total 60K
drwxrws--T 2 root      charybdis 4.0K May 25 21:32 .
drwxr-x--- 8 root      charybdis 4.0K May 25 21:21 ..
-rw------- 1 charybdis charybdis 5.0K Apr 20 04:55 ban.db
-rw-r----- 1 root      charybdis 4.8K Jun 28 09:47 clients.conf
-rw-r----- 1 root      charybdis  595 May 25 21:36 dh3k.pem
-rw-r----- 1 root      charybdis 3.0K Apr  4 00:04 general.conf
-rw-r----- 1 root      charybdis 2.8K May 25 21:21 ircd.conf
-rw-r----- 1 root      charybdis 5.3K May 25 21:29 ircd.crt
-rw-r----- 1 root      charybdis 3.2K May 25 21:24 ircd.key
-rw-r----- 1 root      charybdis 3.0K Jun 10 20:08 ircd.motd
-rw-r----- 1 root      charybdis 2.0K Jun 11 13:25 opers.conf
-rw-r----- 1 root      charybdis 1.1K Apr 20 03:13 servers.conf

[grawity]

Does SQLite really do this? Wouldn't scale well, I imagine.

Though it does need write rights to the directory, but for stuff like ban.db-journal instead.

[aaronmdjones]

Ah yes, SQLite does not do atomic commits by the method I described. It does still need to create a separate file in the directory for every transaction though, and it is by that name, as described in https://www.sqlite.org/atomiccommit.html