Bug#642005: general: maximum size of SHM memory blocks to low
On Sun, Sep 18, 2011 at 10:06:11AM +0000, Yami Shi wrote:
> Package: general
> Severity: grave
> Justification: renders package unusable
>
> I know the program I'll basing this on isn't part of Debian but here it goes.
> I'm an Avast user and in my search for a solution I found that this problem is
> due to the basic kernel variable settings which renders Avast unable to update
> the virus database and probably effects other programs. The people on the Avast
> forums have found a fix but it makes it mandates an extra hook commander to
> make a Debian Live image to find system infections. Here is the forums link for
> the problem and solution: http://forum.avast.com/index.php?topic=57775.0 I hope
> this can be addressed in a update soon so that people can use Debian Live to
> find and remove infections on their computers a little bit better.
Avast is using SYSV SHM. One solution is that it should be using POSIX
SHM which will generally have much less restriction upon the available
memory (defaults to half of the available RAM).
This isn't a grave bug BTW, it's just a configuration detail. In most
cases, 32MIB is more than plenty, and Avast failing when it runs out
is a bug in Avast. It's quite likely that this is due to a design flaw
in Avast in general by having unrealistic expectations and failing to
cope when these aren't met. What on earth does it need all that shared
memory for that couldn't be shared by either
1) having it as a file on disc that all processes can open and map in
2) forking and inheriting the parent's data
3) using POSIX SHM
?
Regards,
Roger
--
.''`. Roger Leigh
: :' : Debian GNU/Linux http://people.debian.org/~rleigh/
`. `' Printing on GNU/Linux? http://gutenprint.sourceforge.net/
`- GPG Public Key: 0x25BFB848 Please GPG sign your mail.
Reply to: