netbsd-users: Re: managing process memory limits on the fly?

Subject: Re: managing process memory limits on the fly?
To: Carl Brewer <carl@bl.echidna.id.au>
From: Jeff Rizzo <riz@NetBSD.org>
List: netbsd-users
Date: 02/21/2007 17:43:01

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig9FCFCEFB03047B21ACCBD6C4
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Carl Brewer wrote:
> ok, thanks.  I tried this on a jammed up zope process, and saw the
> following :
>
> rollcage2# sysctl proc.23242.rlimit.datasize.hard
> proc.23242.rlimit.datasize.hard =3D 1073741824
> rollcage2# sysctl -w proc.23242.rlimit.datasize.hard=3D2147483648
> proc.23242.rlimit.datasize.hard: 1073741824 -> 2147483648
> rollcage2# sysctl proc.23242.rlimit.datasize.hard
> proc.23242.rlimit.datasize.hard =3D 1073741824
>
>
> so it didn't actually do anything.  Did I do something wrong?

You can't raise the "hard" limit - it's the soft limit you want to change=
=2E

+j




--------------enig9FCFCEFB03047B21ACCBD6C4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iQCVAwUBRdz1MLOuUtxCgar5AQPCJAP8CgVSngeluGS/BdvfYQhCaSZTff2UyGO+
dGGjV59nLT3TLUj7GKX4ge+a1Ox0WMw2Bh1nmVbTWu8zC2MATcRrDjf9SOqQI6tr
K4eTUjlVDCYEUlTQR78u0K/8ZZw4AGT5c1aGei1LoEA103X3PrJw0wFns7unD4Kv
OhhB1eGBynM=
=pI4D
-----END PGP SIGNATURE-----

--------------enig9FCFCEFB03047B21ACCBD6C4--