On Wed, 25 Jun 2003 16:44:56 -0400 (EDT)
Robert Watson [EMAIL PROTECTED] wrote:
The code most likely to cause a memory leak in the MAC Framework is
the label management code, since that's the only code that really does
much in the way of memory allocaiton. Try compiling options MAC_DEBUG
On Wed, 25 Jun 2003 16:44:56 -0400 (EDT)
Robert Watson [EMAIL PROTECTED] wrote:
The code most likely to cause a memory leak in the MAC Framework is
the label management code, since that's the only code that really does
much in the way of memory allocaiton. Try compiling options MAC_DEBUG
On Thu, 26 Jun 2003, Socketd wrote:
On Wed, 25 Jun 2003 16:44:56 -0400 (EDT)
Robert Watson [EMAIL PROTECTED] wrote:
The code most likely to cause a memory leak in the MAC Framework is
the label management code, since that's the only code that really does
much in the way of memory
Date: Wed, 25 Jun 2003 19:16:52 +0200
From: Socketd [EMAIL PROTECTED]
Sender: [EMAIL PROTECTED]
Hi all
I have just installed 5.1 Release on my laptop (6gb harddisk and 60 mb
ram). I only installed the base system + man pages and the port
collection. A little info:
/ 128M
Swap
On Wed, 25 Jun 2003 10:24:43 -0700
Kevin Oberman [EMAIL PROTECTED] wrote:
Providing your complete configuration file and /var/run/dmesg.boot
might give a bit of a clue.
Ok. /usr/src/sys/i386/conf/SOCKETD:
machine i386
cpu I586_CPU
ident SOCKETD
options
On Wed, 25 Jun 2003, Socketd wrote:
I have just installed 5.1 Release on my laptop (6gb harddisk and 60 mb
ram). I only installed the base system + man pages and the port
collection. A little info: / 128M Swap 256M /var 128M /var/tmp 256M
(/tmp is symlinked to this) /home 256M /usr The
Just FYI, there are actually some legitimate situations in which
processes will appear to hang when using MAC. For example, if you have
MLS or Biba turned on, and revocation support specifically enabled (not
the default), you can see interactive processes appear to hang when they
are interacting
On Wed, 25 Jun 2003 16:44:56 -0400 (EDT)
Robert Watson [EMAIL PROTECTED] wrote:
Sounds like a memory leak to me; it might also be a locking problem.
Are you actually running with any MAC policies, or just with the
framework?
Just the framework, no policies.
The code most likely to cause a
