--UPT3ojh+0CqEDtpF
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, May 19, 2002 at 11:52:35PM +0200, Soren S. Jorvang wrote:
> On Sun, May 19, 2002 at 06:46:05PM +0100, David Laight wrote:
> > > Yes. SHMMAXPGS should be nuked from orbit -- it should dynamically
> > > size itself. (We should also somehow garbage collect segments that are
> > > no longer associated with running processes.)
> >=20
> > I have a horrid wisper of a memory that they are required to
> > stay lurking....
>=20
> But we could at least make segments whose creator crashes go
> away, as per nasal demons, which I think would go a long way
> in practice.

The creator is allowed, and sometimes supposed, to go away.
shm is a volatile filesystem.

Now, what is really missing is a compiled tool for the admin to look
at defined shm segments, and clean them up if need should be, just like=20
cleaning up /tmp periodically.

I think SunOS has one...=20

Regards,
	-is
--=20
seal your e-mail: http://www.gnupg.org/

--UPT3ojh+0CqEDtpF
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (NetBSD)
Comment: For info see http://www.gnupg.org

iD8DBQE86L2nPCRcZ/VMtk4RAgyWAKCUt4AU13YVVKtQuYFxU0Ee/rm7qgCfbmkm
cURJ5jLsF5xJLFZs/yxvH0s=
=8Beh
-----END PGP SIGNATURE-----

--UPT3ojh+0CqEDtpF--