This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enigCDF012FCB4FC78B4732FDA45
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 8/28/12 3:14 PM, Andy Young wrote:
I am relatively new to using IO monitoring tools and wanted
On 8/29/12 12:07 PM, Daniel Braniss wrote:
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--enigCDF012FCB4FC78B4732FDA45
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
On 8/28/12 3:14 PM, Andy Young wrote:
I am relatively new
All,
I'm trying to determine if this is a bug or for real. We have a customer that
pointed his
NMS at our appliance (running FBSD 9.0). These are 64-bit intel platforms (8
core Xeons)
with 8 Gbytes of RAM and a 16 Gbyte swap.
The customer claims that the NMS shows him that these boxes have a
On Wed, Aug 29, 2012 at 09:09:17AM -0700, Patrick Mahan wrote:
All,
I'm trying to determine if this is a bug or for real. We have a customer
that pointed his
NMS at our appliance (running FBSD 9.0). These are 64-bit intel platforms (8
core Xeons)
with 8 Gbytes of RAM and a 16 Gbyte
http://people.freebsd.org/~imp/MALLOC_DEBUG.diff
This makes WITH/WITHOUT_MALLOC_DEBUG work. The non-standard PRODUCTION_MALLOC
form is retained for compatibility. This also needs to be documented.
Comments?
Warner
___
freebsd-hackers@freebsd.org
On 29 August 2012 20:07, Warner Losh i...@bsdimp.com wrote:
http://people.freebsd.org/~imp/MALLOC_DEBUG.diff
This makes WITH/WITHOUT_MALLOC_DEBUG work. The non-standard
PRODUCTION_MALLOC form is retained for compatibility. This also needs to be
documented.
Comments?
Please!
adrian
6 matches
Mail list logo