From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Ken's file server - insurmountable problem?
Date: Mon, 12 Jan 2004 23:13:17 +0000 [thread overview]
Message-ID: <bd222b30aec3fc782604fa8934b7b7f1@terzarima.net> (raw)
In-Reply-To: <20040112205558.D4316@cackle.proxima.alt.za>
>>and I don't really understand how to get around this problem.
you'll need to type dump periodically during the copy, to flush the cache.
that often works.
the cache typically needs to be larger than the largest potential file
next prev parent reply other threads:[~2004-01-12 23:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-12 18:55 Lucio De Re
2004-01-12 23:13 ` Charles Forsyth [this message]
2004-01-13 5:25 ` Lucio De Re
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=bd222b30aec3fc782604fa8934b7b7f1@terzarima.net \
--to=forsyth@terzarima.net \
--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).