> Keep $max_servers below the point where processes start failing.
> This way, even burst of mail won't crush the system, it will just
> slowly grind its way through a backlog.
>
>
Confirmed - no fork errors - and the postqueue is OK .
> Mark
>
>
Kevin,
> The fork error does not happen on this box - but it does happen on a
> test box which has hardly ant swap space.
Swap space should be cheap even on a virtual machine.
Paging out rarely-used memory sections is not bad.
Swap space provides some living room when RAM gets tight.
Processing m
Mark Martinec wrote:
> Kevin,
>
>
>> We have a virtual machine and adding more RAM is going to be expensive.
>>
>> The server only does email and only looks after the email for a single
>> domain - maybe at the very most a couple of thousand incoming and
>> outgoing emails per day.
>>
>> Is th
>
> What else it taking up the ram? run a top. clamav? just use basic
> sigs, no sane sigs, no google safesigs.
> don't run pyzor,
Will check.
> where is the DNS server? you running a caching dns server on the same
> box? what about httpd? you limit the starting and available processes?
>
Kevin,
> We have a virtual machine and adding more RAM is going to be expensive.
>
> The server only does email and only looks after the email for a single
> domain - maybe at the very most a couple of thousand incoming and
> outgoing emails per day.
>
> Is there any advice on setting the system
Kevin Bailey wrote:
> Hi,
>
> We have a virtual machine and adding more RAM is going to be expensive.
>
How much ram? our 150 user appliances use 384mb ram and run just fine.
if you have less than that, I can't see you even running an os.
our 100 user VPS clusters allocate ~512MB ram to each
Hi,
We have a virtual machine and adding more RAM is going to be expensive.
The server only does email and only looks after the email for a single
domain - maybe at the very most a couple of thousand incoming and
outgoing emails per day.
Is there any advice on setting the system up so is doesn