This reverts commit 5c4ff7af.

The account migration is done, so offsite backups can be re-enabled.

New username; separate and longer account manager + storage passwords.

Also, have to use --remote-path=borg1 when interacting with rsync.net.

Increase default time range from 90 days to 6 months.

rsync.net is about to migrate us to a new username/hostname pair.

This was a regression which has been fixed upstream.

This reverts commit 67e7677e.

We're no longer allowed to reserve formerly used namespaces.

Grafana v8.2.0 added support for Prometheus's Alertmanager[1] which can
be used with the Unified Alerting added in v8.0.0[2].

[1] https://github.com/grafana/grafana/releases/tag/v8.2.0
[2] https://grafana.com/blog/2021/06/08/grafana-8.0-unified-grafana-and-prometheus-alerts-live-streaming-new-visualizations-and-more/

Mostly changes from Grafana v8.0[1].

[1] https://grafana.com/docs/grafana/latest/whatsnew/whats-new-in-v8-0/

The security tracker is not compatible yet with the new sqlalchemy, use
the old version in our repos

Useful for mail.archlinux.org where this setting doesn't matter since we
force the SSH command to passwd and zsh was removed as part of the tools
cleanup effort recently (stops shadow.service from complaining about zsh
missing).

sort + groupby fanciness by @klausenbusk.

A string is always "true"[1].

[1] https://stackoverflow.com/a/34868470

Fix #392

Thorben Günther authored 3 years ago and Kristian Klausen committed 3 years ago

shell is like command but runs the command through a shell, so that
piping will work.

Jakub Klinkovský authored 3 years ago and Kristian Klausen committed 3 years ago

We've hit this problem at least twice in the past, last time with the new
Vector skin update. With this change it should not be necessary to do
anything manually after an update.

Jan Alexander Steffens (heftig) authored 3 years ago and Kristian Klausen committed 3 years ago

- When loki hits 5.5G RSS, aggressively reclaim its memory. This puts
  it under memory pressure.
- When loki hits 6G RSS, invoke the kernel OOM killer.
- When loki is under severe memory pressure, have systemd-oomd kill it.

Jan Alexander Steffens (heftig) authored 3 years ago and Kristian Klausen committed 3 years ago

- Allow killing of any cgroup if swap is about to run out. When swap is
  at least 90% full, oomd will kill a cgroup, tending to kill the cgroup
  with the highest swap usage.
- Allow killing cgroups of logged in users under severe memory pressure.
  When a cgroup is stalled waiting for memory at least 60% of the time,
  for at least 30 seconds, oomd will attempt to kill it or one of its
  descendant cgroups.