From: Patrick O'Rourke <porourke@egenera.com>
To: Adrian Phillips <a.phillips@met.no>
Cc: reiserfs-list@namesys.com
Subject: Re: rsync and memory leak on linux 2.2?
Date: 14 Feb 2003 09:04:51 -0500 [thread overview]
Message-ID: <1045231491.17182.9.camel@barnes> (raw)
In-Reply-To: <87r8abtlhq.fsf@freeze.oslo.dnmi.no>
On Fri, 2003-02-14 at 01:38, Adrian Phillips wrote:
> Well, there is a 3.5.34 which has, obviously, a number of bug
> fixes. You could try that. I've been running 2.2.20 with this version
> for a good number of months on several servers with no problems.
That's a thought. We've been running w/ 3.5.32 (+ a variety of fixes)
for over a year and this is the only issue we have thus far and it only
occurs in an isolated scenario (i.e. rsync).
Thanks for the suggestion.
Pat
--
Patrick O'Rourke
porourke@egenera.com
prev parent reply other threads:[~2003-02-14 14:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-13 17:11 rsync and memory leak on linux 2.2? Patrick O'Rourke
2003-02-13 19:15 ` Oleg Drokin
2003-02-14 6:38 ` Adrian Phillips
2003-02-14 10:01 ` Oleg Drokin
2003-02-14 10:09 ` Adrian Phillips
2003-02-19 21:24 ` Patrick O'Rourke
2003-02-19 22:18 ` Hans Reiser
2003-02-20 6:19 ` Oleg Drokin
2003-02-14 14:04 ` Patrick O'Rourke [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=1045231491.17182.9.camel@barnes \
--to=porourke@egenera.com \
--cc=a.phillips@met.no \
--cc=reiserfs-list@namesys.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.