You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Sayan 952c5caa86 Poison the database by default if snapshotting fails (#160) ... * Stop accepting writes if snapshotting fails This is an important consideration: if BGSAVE fails and poisons the database, snapshotting can and should too. But this is debatable in some parts. For example, users may configure snapshots to be on a network file system (symlinked maybe) and this can fail. Now in some cases, this failure 'may be acceptable'. This commit adds a way to customize this behavior through the `failsafe` key in the snapshots section of the cfg file and through the --stop-write-on-fail option passed to `skyd` on startup. However, BGSAVE remains unchanged: it will always poison the database if it fails. If the user doesn't want this, they can simply disable BGSAVE. * Add changelog		3 years ago
..
badcfg.toml	Add module to handle configuration files	4 years ago
badcfg2.toml	Enable bgsave config to be read from the cfg file	4 years ago
bgsave-justenabled.toml	Make `every` and `enabled` keys in bgsave optional	4 years ago
bgsave-justevery.toml	Make `every` and `enabled` keys in bgsave optional	4 years ago
ipv6.toml	Add support for IPv6 addressing	4 years ago
secure-noart.toml	Added port, host and noart options in config file	4 years ago
skyd.toml	Fix outdated comments and ident naming	4 years ago
snapshot.toml	Rebrand from TerrabaseDB to Skybase (#90)	4 years ago
ssl.toml	Enable TLS port to be set and impl `MultiListener`	4 years ago
template.toml	Poison the database by default if snapshotting fails (#160)	3 years ago
withcustombgsave.toml	Cleanup to use `BGSave` as a configuration object	4 years ago