Syncoid uses `pv` to display information about transfer speeds. During
the pv bump from 1.10.5 to 1.11.0 it started using the setitimer syscall
(included by `@timer`) which would segfault given that the sandbox
configuration was set to block all syscalls in the `@timer` group
Release notes ("What's new"):
https://www.ibm.com/docs/en/storage-protect/8.2.1?topic=whats-new#r_wn_tsmserver__title__3
The package now needs `brotli` and `libnghttp2`.
Unfortunatelly, the vm test's OCR no longer recognizes
the version number in the information dialog box
(it sees "8.21.0" instead of "8.2.1.0").
I don't think relaxing that test makes any sense,
as OCR might fail in a million different ways.
So I just remove the version number check from the test.
To avoid confusion and spurious newlines in the output.
Found by searching for a backslash followed by a newline, some
indentation, and then the end of multi-line string marker, using the
following extended regex:
```regex
\\\n +'';
```
in order to allow binding to not (yet) locally available
interfaces. man 5 systemd.socket says:
> For robustness reasons it is recommended to use this option
> whenever you bind a socket to a specific IP address.
Add an option `service.borgbackup.jobs.<name>.dumpCommandProducesTar`
that allows using `borg import-tar` rather than `borg create` to import
an archive.
Add an option `service.borgbackup.jobs.<name>.wrapper` that allows to
control the name of the installed wrapper script -- or even to disable
its installation at all.
Signed-off-by: Sefa Eyeoglu <contact@scrumplex.net>
These settings are documented here:
https://pgbackrest.org/configuration.html
It's useful to be able to define specific configuration for separate
commands, for example for fixing a failing test in the next update.
The new `\restrict` migitation creates random keys in the dump file by
default, which breaks a before/after test for the backup module. By
making the restrict key reproducible, the test passes again.
Add module support for --stdin-from-command flag, which was added to
restic in https://github.com/restic/restic/pull/4410. I also made a few
very small changes here and there in the nix code to make it look a
little neater in my opinion.
I could potentially add support for the --stdin flag too, but this would
require prepending the restic command with an external command and a
pipe, which seems a bit messy - and the restic documentation says to
prefer --stdin-from-command over --stdin anyway.
I could add an option for --stdin-filename, but I feel that this would
be better for users to do in extraBackupArgs.
This avoids restarting the postgresql server, when only ensureDatabases
or ensureUsers have been changed. It will also allow to properly wait
for recovery to finish later.
To wait for "postgresql is ready" in other services, we now provide a
postgresql.target.
Resolves#400018
Co-authored-by: Marcel <me@m4rc3l.de>
