9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jack Johnson <fragment@nas.com>
To: 9fans@cse.psu.edu
Subject: [9fans] Venti: bad format in version string?
Date: Tue,  2 Jul 2002 08:18:56 -0700	[thread overview]
Message-ID: <3D21C460.9090606@nas.com> (raw)

Sean Quinlan wrote:
> somehow, you managed to connect to the port serving the
> the venti protocol rather than the http port.
> 
> seanq
>> 
>> I've set up my first Venti server on a standalone workstation, and
>> while it's still running through its first test, I've tried to access
>> its Web server and I get a lone line in response:
>> 
>>   venti-02-libventi

Yes, I realized after posting that I'm a complete idiot.

Here's the play-by-play: I set up venti, fired it up, shovelled some 
data, went to check it's internal Web server and noted the lack of 
response from port 80, so I portmapped it, found the open venti port, 
and connected to it.  Thus my shameful explication of my inability to 
read documentation ("Help!  I've fallen and I can't RTFM!").

For the record, though the man page says it will listen to tcp!*!http by 
default, I found that I had to use the -h option for the internal Web 
server to start.  The likelihood that my workstation isn't 
well-configured is high, though.

In a networked Plan 9 environment, are people running venti on a 
terminal?  On a CPU server?  I know fs is going through some revision, 
but it's clear that some people are using venti regularly, and I'd love 
to know how it's being used inside and outside the Labs.

-Jack



             reply	other threads:[~2002-07-02 15:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-02 15:18 Jack Johnson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-07-02  8:53 Jack Johnson
2002-07-02 11:11 ` Sean Quinlan

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=3D21C460.9090606@nas.com \
    --to=fragment@nas.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).