From: geoff@plan9.bell-labs.com
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9fs nvr file
Date: Thu, 17 Aug 2006 02:26:43 -0400 [thread overview]
Message-ID: <b4f50a589fa2571ac9164991f1e7c277@plan9.bell-labs.com> (raw)
In-Reply-To: <e4e2cf0c5886da8469e3b73486a78ba7@quanstro.net>
Right, I'd forgotten about noauth.
Sure, send in the nvr patch and I'll look at it.
I think the worm writer is trying to avoid monopolising the jukebox so
that others can use it while the dump is running. Of course, if you
have a large magnetic disk cache, this is unlikely to be an issue. If
you're really lucky, your working set of data will fit in the file
server's RAM.
next prev parent reply other threads:[~2006-08-17 6:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-15 19:09 erik quanstrom
2006-08-15 19:32 ` erik quanstrom
2006-08-15 19:35 ` geoff
2006-08-15 19:42 ` erik quanstrom
2006-08-16 3:36 ` erik quanstrom
2006-08-16 13:30 ` erik quanstrom
2006-08-16 17:38 ` geoff
2006-08-16 18:11 ` erik quanstrom
2006-08-16 18:27 ` geoff
2006-08-16 18:51 ` erik quanstrom
2006-08-17 2:22 ` geoff
2006-08-17 6:20 ` erik quanstrom
2006-08-17 6:26 ` geoff [this message]
2006-08-17 6:40 ` erik quanstrom
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=b4f50a589fa2571ac9164991f1e7c277@plan9.bell-labs.com \
--to=geoff@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).