All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Friesen <cfriesen@nortelnetworks.com>
To: linux-kernel@vger.kernel.org
Subject: Re: help...where is my memory going? --soln found...sysv shared mem
Date: Fri, 16 May 2003 14:57:49 -0400	[thread overview]
Message-ID: <3EC534AD.5080604@nortelnetworks.com> (raw)
In-Reply-To: 3EC52BC1.7070003@nortelnetworks.com


Some of the stuff that had already started up was using sysv shared memory 
segments, and they didn't get cleaned up properly.  Accounts for all the memory 
usage that I was trying to figure out.

Thought I'd post the solution in case anyone else gets hit by something similar.

Chris

-- 
Chris Friesen                    | MailStop: 043/33/F10
Nortel Networks                  | work: (613) 765-0557
3500 Carling Avenue              | fax:  (613) 765-2986
Nepean, ON K2H 8E9 Canada        | email: cfriesen@nortelnetworks.com


  reply	other threads:[~2003-05-16 18:45 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-16 18:19 help...where is my memory going? Chris Friesen
2003-05-16 18:57 ` Chris Friesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-05-17  2:44 help...where is my memory going? --soln found...sysv shared mem Chuck Ebbert

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3EC534AD.5080604@nortelnetworks.com \
    --to=cfriesen@nortelnetworks.com \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.