From: Nathaniel W Filardo <nwf@cs.jhu.edu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] when to use vac -q -d old.vac instead of simply vac -d old.vac
Date: Wed, 1 Jul 2009 21:54:24 -0400 [thread overview]
Message-ID: <20090702015424.GC25893@gradx.cs.jhu.edu> (raw)
In-Reply-To: <dd6fe68a0906290856q3aacb3a8g86bd76ca4063114e@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 362 bytes --]
On Mon, Jun 29, 2009 at 08:56:06AM -0700, Russ Cox wrote:
> Whether you use -q should have no effect on the memory usage.
> There may be a memory leak somewhere involving -q, but at
> first glance I don't see one. Feel free to investigate.
You're right; I glitched. The memory consumption is due to -d, not -q, of
course. Sorry for the noise.
--nwf;
[-- Attachment #2: Type: application/pgp-signature, Size: 204 bytes --]
prev parent reply other threads:[~2009-07-02 1:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-29 1:13 Fernan Bolando
2009-06-29 5:02 ` Nathaniel W Filardo
2009-06-29 12:23 ` [9fans] when to use vac -q -d old.vac instead of simply vac -dold.vac erik quanstrom
2009-06-29 15:56 ` [9fans] when to use vac -q -d old.vac instead of simply vac -d old.vac Russ Cox
2009-07-02 1:54 ` Nathaniel W Filardo [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=20090702015424.GC25893@gradx.cs.jhu.edu \
--to=nwf@cs.jhu.edu \
--cc=9fans@9fans.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).