Hi MattGood,
To recap:
a) The default maximum size of a shared memory block segment or shmmax is set in the linux kernel (32Mb in the case of Ubuntu) by the linux kernel maintainers? (i.e hardcoded).
b) However, this shmmax value can be revised via issuing the command after the boot up process:
sysctl -w kernel.shmmax=128000000
or
echo 128000000 >/proc/sys/kernel/shmmax
To automate the process, see :
http://forum.avast.com/index.php?topic=57775.msg486945#msg486945.
c) The value of the shmmax can be revised e.g from 128000000 to 133120000 or a higher value as time goes by to accommodate later changes in vps.400 (avast definitions).
d) I am setting the shmmax value to as high as I think it will work in order to minimise this issue from recurring again.
f) As long as this limitation is in play between avast vps.400 and the shmmax limit, we will encounter the same error in the future when it is exceeded.
g) My guess is this solution is a "workaround".
Best Regards