GnuPG + FreeBSD 5.3 = intermitent memory warning
atom at suspicious.org
Wed Dec 15 07:28:16 CET 2004
-----BEGIN PGP SIGNED MESSAGE-----
i'm curious if OS-X has the same bug... has anyone checked to see if the
error can be duplicated under similar conditions?
On Tue, 14 Dec 2004, David Shaw wrote:
> It took me a while to track this down, and thanks to Atom for helping me
> run some FreeBSD tests. It turns out that this isn't a GnuPG specific
> problem. The same problem can be duplicated by running any program that
> calls mlock() on FreeBSD.
> FreeBSD has a "1/3 of memory" hard limit for mlock(). What seems to
> have happened is that for whatever reason, Atom's system was very close
> to the 1/3 magic number, and so when GnuPG tried to get its lock, it was
> sometimes refused. This also explains why a busy system seemed to
> aggravate the problem.
> In terms of what to do about this in GnuPG, I'm not sure if there should
> be anything done. I think the the current GnuPG behavior is pretty
> good: try to get locked memory, and if it can't, warn the user.
PGP key - http://atom.smasher.org/pgp.txt
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
"Some folks look for answers
others look for fights,
some folks up in treetops
just looking for their kites"
-- Grateful Dead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.3.93 (FreeBSD)
Comment: What is this gibberish?
-----END PGP SIGNATURE-----
More information about the Gnupg-devel