From: Chris Rose <offline@shaw.ca>
To: Ray Olszewski <ray@comarre.com>
Cc: linux-newbie@vger.kernel.org
Subject: Re: Memory leaks and strange results from top
Date: Sun, 08 Feb 2004 17:02:36 -0700 [thread overview]
Message-ID: <4026CE1C.7080703@shaw.ca> (raw)
In-Reply-To: <5.1.0.14.1.20040208093437.01f2f778@celine>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Thanks, Ray, for the thoroughly detailed response.
Following up on some of the things you've mentioned, i did some googling
and now i think i get it - i'm not too familiar with the way that linux
reports memory usage, so it caught me off guard.
As far as ClarkConnect itself is concerned, it's a modified RH8 derivate
that is intended for use purely as a firewall/gateway and nothing else.
~ I was experiencing intense performance problems on it previously with
96Mb, although i had been assured that it should run just fine with that.
So, post-upgrade, i was shocked to see memory use up again.
At any rate, there's no performange problem with the new setup, but
since i thought it was a program problem, I was figuring i'd fix it
preemtively. Thanks again for the very educational reply.
Cheers.
- --
Chris R.
=======
http://offlineblog.com/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFAJs4cYGWCRcy3UcsRAtAoAJ4x8Ga2w5Q6Ho1g9QZnKEItfj6tHACgiD56
ZMZcgkuuf1iyINeGfq2LWEU=
=BvAl
-----END PGP SIGNATURE-----
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs
prev parent reply other threads:[~2004-02-09 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-08 17:03 Memory leaks and strange results from top Chris Rose
2004-02-08 18:11 ` Ray Olszewski
2004-02-09 0:02 ` Chris Rose [this message]
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=4026CE1C.7080703@shaw.ca \
--to=offline@shaw.ca \
--cc=linux-newbie@vger.kernel.org \
--cc=ray@comarre.com \
/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.