On 11/6/19 7:53 AM, Dimitris via Dng wrote:
On 11/6/19 3:45 PM, hal wrote:
I've installed the libc6-dev-i386 package to see if it solves it but then I
wondered what is spamassasin doing compiling things anyway?
https://packages.debian.org/stretch/sa-compile
Thanks. I reinstalled the p
How stable is beowulf? Is there people using it in production?
It is stated on https://devuan.org/os/releases:
Beowulf -> In development
I suppose it is equivalent to "testing".
"testing is where the next stable suite is developed. Software is
usually more up-to-date but there may still be is
On 11/7/19 2:01 PM, hal wrote:
> 172609 0 lrwxrwxrwx 1 root root 31 Feb 6 2019
> /usr/include/sys/types.h -> ../x86_64-linux-gnu/sys/types.h
i think the problem is there.. symlink(?) to non-existent file..
in a debian stretch system (got no ascii with spamassassin avail
I installed Beowulf over Ascii several months ago and want to report
general success.
However, there was a glitch I do not understand. I could not get SMTP
authentication (I'm running exim4 and mutt). Turned out that exim
could not read my etc/eximr4/passwd.client file. Its ownership and
perm
On Thu, 7 Nov 2019 13:13:38 +0100
Bernard Rosset via Dng wrote:
> - Even though I use scripts to automatically save/restore ip(6)tables
> rules on up/down, I ended up having my rules cleared through initial
> reboots. No precise idea on why.
> I suggest you always keep a manual save of them so
On 07/11/2019 12:13, Bernard Rosset via Dng wrote:
How stable is beowulf? Is there people using it in production?
I have 20+ hosts all running Beowulf, including production DNS servers,
email servers, MySQL (MariaDB) servers, web servers, firewalls, routers
and Asterisk PBXes on mainly Del
On 11/7/19 6:39 AM, Dimitris wrote:
On 11/7/19 2:01 PM, hal wrote:
172609 0 lrwxrwxrwx 1 root root 31 Feb 6 2019
/usr/include/sys/types.h -> ../x86_64-linux-gnu/sys/types.h
i think the problem is there.. symlink(?) to non-existent file..
in a debian stretch syste
Beowulf/Buster has moved from iptables to nftables. You can still use
iptables* with iptables-legacy*, but you'll need to edit your scripts
to reflect this. The option to save existing rules is part of the
upgrade but assumes that the existing rules haven't already been
overwritten with the defau
