From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] connecting venti: no route
Date: Sat, 9 Dec 2006 09:22:01 -0500 [thread overview]
Message-ID: <20061209142201.3A0ED21E994@medicine-bow.quanstro.net> (raw)
In-Reply-To: <a1b085bde80ce2ed58a9a31b94810be3@proxima.alt.za>
in a similar vein, why does one need tcp to connect venti
server and client. i tried connecting fossil to venti via il!127.1!venti.
fossil started complaining that the venti server wasn't there in just
a few minutes.
the venti manual page says
A Venti server is accessed via an undocumented network pro-
tocol. [...]
but what are the requrirements on the network connection between
venti client and server? naïvely, one would guess the lack of flow
control could be the problem. but naïvely one would also guess that
the undocumented protocol, like 9p, is a ping-pong protocol that
doesn't need flow control.
what am i missing?
- erik
Lucio De Re <lucio@proxima.alt.za> writes
|
| > changed the line in plan9.ini to venti=/dev/sdC0/arenas tcp!*!17034
| > tcp!127.1!8000
|
| In plan9.ini, venti=tcp!127.1!17034 ought to be correct. Also, make
| sure you
|
| ip/ipconfig loopback /dev/null 127.1
|
| in /rc/bin/cpurc before initialising venti. I don't think you need to
| go to the same lengths as I did, but this is what I have at hand:
|
| if (~ $venti '') {
| loop=127.1
| ip/ipconfig loopback /dev/null $loop
| vhost=tcp!$loop
| venti=$vhost^!venti
| venti/venti -c venti.conf -B 1m -C 1m -h $vhost^!80 -I 1m -w -a $venti || {
| echo Venti startup failed: $status
| exit venti
| }
| }
|
| I can't vouch for plan9.ini, because I don't have access to the
| equipment that uses the above, so it may even be out of date.
|
| ++L
next prev parent reply other threads:[~2006-12-09 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-09 12:39 Matthias Teege
2006-12-09 13:09 ` Lucio De Re
2006-12-09 14:22 ` erik quanstrom [this message]
2006-12-09 14:38 ` Steve Simon
2006-12-09 19:16 ` Georg Lehner
2006-12-09 22:41 ` erik quanstrom
2006-12-09 16:36 ` Heiko Dudzus
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=20061209142201.3A0ED21E994@medicine-bow.quanstro.net \
--to=quanstro@quanstro.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).