Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

For some reason printf doesn't error if zabbix_sender dies. Try if
syswrite does.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

A new archweb release has not been made yet with the donor import
integration.

Add donor import service, which imports donors from a maildir directory
in /home/donate/. The emails are dumped using a script on orion which
calls doveadm to create a directory with exported emails.

The workaround for ignore_errors has been fixed in Ansible 2.1.1.0.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

This makes the security tracker role idempotent.

The security tracker renamed app to tracker and needs an ngnix config
and uwsgi config change.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

This is the same as used on luna and as expected by the zabbix nginx
monitoring service.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Otherwise discovery rules don't seem to work for dependent items.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

We might want to monitor client/table/index stats in the future too
without having to change the zabbix item configs.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

If the service is started before the config is copied, we can't recover
from a typo in the config file because maraidb will refused to start. At
least not without manually fixing that typo. This way the typo can be
fixed in ansible and then deployed normally.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

speps: https://lists.archlinux.org/pipermail/aur-general/2018-January/033763.html

faidoc: https://lists.archlinux.org/pipermail/aur-general/2018-January/033764.html



Signed-off-by: Florian Pritz <bluewind@xinu.at>

Eli Schwartz authored 7 years ago and Bartłomiej Piotrowski committed 7 years ago

Rather than explicitly listing each command allowed, match any
executable of the form /usr/bin/*-x86_64-build -- this will only ever be
a symlink to archbuild which is all we are looking for.

devtools allows new archbuild configurations to be easily added by
creating a symlink of the form ${config}-${arch}-build and adding the
relevant /usr/share/devtools/pacman-${config}.conf

This change allows the sudoers policy to automatically support these, in
the event that devtools distributes new archbuild configs or a sysadmin
adds a custom one.

Just turn stupid non-UTF-8 refs into garbage instead of crashing.

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>

Signed-off-by: Florian Pritz <bluewind@xinu.at>