On 01/28/2015 05:00 PM, Reindl Harald wrote:
BTW it is not visible which users are core-developers on this list and
which are not - until now i thought you are as example
I am part of the dev team or as you say "core-developers" which doesn't
mean I have to be a Perl monger. There's other task
Am 28.01.2015 um 16:52 schrieb Axb:
On 01/28/2015 04:38 PM, Reindl Harald wrote:
is AFAIK relevant in context of sa-learn to not re-train the same
messages again and again - and it has it's own bugs becaue for a few
messages it contains random parts of the message itself, fire sa-learn
on the
Am 28.01.2015 um 16:39 schrieb Axb:
On 01/28/2015 03:58 PM, Reindl Harald wrote:
* third: if you would be a smart upstream in case of a company admin
asking for a change instead "write a patch" you could make
a offer talking about money to include the change in the
On 01/28/2015 04:38 PM, Reindl Harald wrote:
is AFAIK relevant in context of sa-learn to not re-train the same
messages again and again - and it has it's own bugs becaue for a few
messages it contains random parts of the message itself, fire sa-learn
on the whole corpus would add these messages
On 01/28/2015 03:58 PM, Reindl Harald wrote:
* third: if you would be a smart upstream in case of a company admin
asking for a change instead "write a patch" you could make
a offer talking about money to include the change in the
next upstream version - we sponso
Am 28.01.2015 um 16:24 schrieb Axb:
On 01/28/2015 03:58 PM, Reindl Harald wrote:
* first: it is a bug to write/lock when auto_expire / auto_learn is off
bayes_seen
is AFAIK relevant in context of sa-learn to not re-train the same
messages again and again - and it has it's own bugs becau
On 01/28/2015 03:58 PM, Reindl Harald wrote:
* first: it is a bug to write/lock when auto_expire / auto_learn is off
bayes_seen
On Wed, 2015-01-28 at 15:04 +0100, Reindl Harald wrote:
> no need for mount own partitions on recent linux systems
> that's what namespaces are for and systemd has easy interfaces
>
Fair enough: I thought you were talking about some sort of site-wide
read-only mount, but using systemd to limit the
Am 28.01.2015 um 15:46 schrieb Axb:
On 01/28/2015 03:18 PM, Kevin A. McGrail wrote:
On 1/28/2015 9:04 AM, Reindl Harald wrote:
my main point is that i don't want the locking IO when nothing then
the self developed maintainance scripts for the bayes has a business
to write anything there - it s
On 01/28/2015 03:18 PM, Kevin A. McGrail wrote:
On 1/28/2015 9:04 AM, Reindl Harald wrote:
my main point is that i don't want the locking IO when nothing then
the self developed maintainance scripts for the bayes has a business
to write anything there - it should be only read and in the best cas
On 1/28/2015 9:04 AM, Reindl Harald wrote:
my main point is that i don't want the locking IO when nothing then
the self developed maintainance scripts for the bayes has a business
to write anything there - it should be only read and in the best case
from each spamc-forker only opened once in hi
Am 28.01.2015 um 12:11 schrieb Martin Gregorie:
On Tue, 2015-01-27 at 16:40 -0800, John Hardin wrote:
On Wed, 28 Jan 2015, Reindl Harald wrote:
if understand you correctly we agree that there is no reason /var can't be
mounted read-only?
Other than the historical practice that /var is inten
On Tue, 2015-01-27 at 16:40 -0800, John Hardin wrote:
> On Wed, 28 Jan 2015, Reindl Harald wrote:
>
> > if understand you correctly we agree that there is no reason /var can't be
> > mounted read-only?
>
> Other than the historical practice that /var is intended to contain
> varying data, and t
13 matches
Mail list logo
