The new sqlite3_rsync command can create a REPLICA of an SQLite database:
$ sqlite3_rsync ORIGIN REPLICA ?OPTIONS?
But why not simply use the rsync command?
The reason is that ordinary rsync does not understand SQLite transactions, can lead to a corrupted copy depending on the database active transactions.
“DanGer@ and myself have migrated the forums over to a new server with bigger specs, running on FreeBSD 14/ZFS, Nginx, MariaDB, PHP 8.3.
The forums software itself (XenForo) will be brought to the latest version at a later date.
Forum plug-ins should work, no longer work, or work again soon”
Was about to report this, but it got fixed: https://github.com/freebsd/freebsd-src/commit/c2ba66d4d01f23303352bfe3cbd50ff5d9a05947
A very alarming ssh warning and it’s solution.
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Solution: ssh-keygen -R <host>, in my case ssh-keygen -R FreeBSD.
-R hostname Removes all keys belonging to hostname from a known_hosts file. This option is useful to delete hashed hosts (see the -H option above).
/root 