From: Richard Miller <9fans@hamnavoe.com>
To: 9fans@9fans.net
Subject: Re: [9fans] tcp!
Date: Sun, 19 Aug 2012 14:17:38 +0100 [thread overview]
Message-ID: <8e880326157a6d461f4cb271dec43034@hamnavoe.com> (raw)
In-Reply-To: <1835b565a7a0babdf4dc6f2787284674@brasstown.quanstro.net>
Within the last month or so I've been having trouble copying large
files to remote servers e.g. sources. The cp process hangs for
many minutes and eventually ends in 'mount rpc error'. I was
hoping this tcp patch might solve it, but alas no.
Has anyone else been observing this?
next prev parent reply other threads:[~2012-08-19 13:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-18 20:11 erik quanstrom
2012-08-18 20:26 ` erik quanstrom
2012-08-19 13:37 ` Richard Miller
2012-08-19 13:55 ` cinap_lenrek
2012-08-19 14:05 ` Richard Miller
2012-08-19 15:07 ` erik quanstrom
2012-08-19 14:48 ` erik quanstrom
2012-08-19 13:17 ` Richard Miller [this message]
2012-08-19 15:43 ` erik quanstrom
2012-08-21 18:32 Richard Miller
2012-08-22 17:18 ` Gorka Guardiola
2012-08-22 18:29 ` Steven Stallion
[not found] ` <CAGGHmKFokgrbH1P_j+31teoO9ubEvLu2Ti7_QP1+WPLXQ291Mg@mail.gmail.c>
2012-08-22 18:46 ` 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=8e880326157a6d461f4cb271dec43034@hamnavoe.com \
--to=9fans@hamnavoe.com \
--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).