On Mon, 07 Jun 2021 14:22:48 +1000 Russell Coker
wrote:
> Package: postfix-policyd-spf-perl
> Version: 2.011-1.1
> Severity: normal
>
>
https://www.getmailbird.com/what-spf-resources-are-available-now-that-openspf-org-is-gone/
>
> According to the above URL openspf.org disappeared in early 201
Clientupdate is never enabled by default!
As long as no "clientversion:" are defined in the file client-local.cfg on
xymon server, clientupdate makes nothing.
If that's a server-side setting, it doesn't change the security
concerns on the client side at all.
Christoph
Possible additional set
Am 07.06.2014 20:05, schrieb Christoph Berg:
In FHS-compliant installations, updating files spread all over the
filesystem is a pretty scary idea.
Axel was satisfied with /var/lib/xymon...
/var/lib/xymon is also $HOME for xymon user.
Would both be happy with /var/run/xymon?
If you really w
Am 06.06.2014 13:42, schrieb Axel Beckert:
Hi Alex,
Alexander Bech wrote:
It is a feature that does not work.
Yes. A feature which is rather incompatible with the concept of
packaging. And incompatible with multiple architectures, too.
The problem could possibly be solved by adding this
Am 05.06.2014 15:37, schrieb Axel Beckert:
Hi Alex,
Alexander Bech wrote:
the client update process from a central plugins-repository fails.
Just to be sure: That's not a regression, right? Did it work in the
past? Or have you tried that feature just the first time?
In the follow
Package: xymon-client
Version: 4.3.17-2
Severity: normal
Dear Maintainer,
the client update process from a central plugins-repository fails.
In the client-local.cfg on the central xymon-server, the following is
configured:
[linux]
clientversion:xc.v3
This tar-file contains tree plugins.
I had the same problem.
Solved by commenting out the line
source-directory /etc/network/interfaces.d
in /etc/network/interfaces.
Alex
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
7 matches
Mail list logo
