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.
7349e461e6
This is very useful because it removes the need for user intervention in the event save on termination fails. Say the save operation fails due to 'some bad daemon' changing the directory's perms. Now skyd reports this error while trying to save upon termination. Our sysadmin now fixes the perms issue. The previous design would force the sysadmin to _somehow_ foreground skyd and hit enter. That is silly. The new design just attempts to do a save operation every 10 seconds. So in case the issue is fixed, the save operation will recover on its own. Why not exponential backoff? That's because the issue can be fixed some long time later and we may have reached a large backoff value so the save that could have succeeded would have to wait for a long duration before it can do anything meaningful. This also fixes a bug that caused BGSAVE errors to be reported as info class log entries. |
3 years ago | |
|---|---|---|
| .. | ||
| native | 3 years ago | |
| src | 3 years ago | |
| Cargo.toml | 3 years ago | |
| build.rs | 3 years ago | |