On 2009-07-27 23:00, Michael Rogers wrote:
> Török Edwin wrote:
>
>> Its not different from allowing any other program unconstrained amount
>> of resources.
>> Try writing a program that does malloc in a loop, or opens a file and
>> writes to it in an infinite loop.
>>
>> To sum up, it is not re
Török Edwin wrote:
> Its not different from allowing any other program unconstrained amount
> of resources.
> Try writing a program that does malloc in a loop, or opens a file and
> writes to it in an infinite loop.
>
> To sum up, it is not recommended to turn off limits in a production
> environm
On 2009-07-27 21:19, Michael Rogers wrote:
> The clamd.conf manpage gives dire warnings about "severe damage to the
> system" if MaxScanSize and MaxFileSize are disabled or set too high.
>
Here are some scenarios:
The partition that has $TMPDIR might get filled if limits are disabled,
preventi
The clamd.conf manpage gives dire warnings about "severe damage to the
system" if MaxScanSize and MaxFileSize are disabled or set too high.
Could anyone please give me a bit more information about what kind of
damage might be involved, and how to choose safe non-default values for
these settings?
Hi Edwin,
2009/7/24 Török Edwin :
> On 2009-07-24 01:26, cas...@gmail.com wrote:
>> Hi,
>>
>> I need some help to understand this issue.
>>
>> We are using safebrowsing.cvd (postfix/amavisd/clamd) and we
>> started to get problems with two newsletters here [1] [2]
>>
>> Messages are in HT
