False insecure memory warnings...

[gabriel rosenkoetter]

--Y9FGoQKSF2AxjRbT
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 04, 2003 at 04:31:39PM -0500, David Shaw wrote:
> util/secmem.c.  In particular see lock_pool().

I'll go dig. Some time other than when I'm about to go out dinner on
a Friday night. :^>

> I wonder if the BSD login.conf rlimit stuff might be biting you here.

Plausible. Well, actually... not:

default:\
[...]
  :memorylocked=3Dunlimited:\

Only other setting's for root...

> If cron has a smaller "memorylocked" value than you do when running
> from the shell, then the mlock call can fail and cause the symptoms
> you see.

Don't think that cron's environment would be smaller, especially
since it's doing a seteuid to the user...

> I do know there was a change to the NetBSD cron recently to
> have it start using login_cap, but I don't know what release that was
> in.

True, and I *believe* that's part of the 1.6 release, but I'm not
positive.

--=20
gabriel rosenkoetter
gr@eclipsed.net

--Y9FGoQKSF2AxjRbT
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (NetBSD)

iD8DBQE+jjui9ehacAz5CRoRAvFDAJ9tjJHjhwt7SkpuFd73dIqre5esFQCdEl3e
l4mLmp1WQSm7i3TQQB4HMuk=
=C2rl
-----END PGP SIGNATURE-----

--Y9FGoQKSF2AxjRbT--