From: "Russ Cox" <rsc@swtch.com>
To: weigelt@metux.de, 9fans@9fans.net
Subject: Re: [9fans] plan9port: tcp servers
Date: Sun, 1 Jun 2008 10:26:13 -0400 [thread overview]
Message-ID: <20080601142556.C91931E8C1F@holo.morphisms.net> (raw)
In-Reply-To: <20080601132825.GB18897@nibiru.local>
> BTW: I've now mounted an vacfs from Midnight Command :)
> But when trying to overwrite, it causes mc to hang. Could it be
> that vacfs drops certain messages instead of returning an
> appropriate error ?
you can run
verbose9pserve=2 vacfs ...
and you will get a lot of debugging messages on standard error.
among other things, you'll get a trace of all the 9p traffic,
and you can check whether this is true. i doubt very much
that vacfs is dropping messages, since it is a single-threaded
server with a simple
for(;;){
read request
response = handle(request);
write response
}
loop.
>> i had considered not requiring the unix! once,
>> but i decided against it.
>
> That would be fine, why did you decied against ?
network addresses and files are different kinds of names.
mixing them would introduce ambiguities, like what
if i have a file name 'tcp!bell-labs.com!http'.
also there was no obvious error response if you
dial "a!b!c!d!e". is it a malformed address?
not if a file name a!b!c!d!e exists. but in general, yes.
russ
next prev parent reply other threads:[~2008-06-01 14:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 12:35 Enrico Weigelt
2008-05-27 14:44 ` Russ Cox
2008-06-01 10:45 ` Enrico Weigelt
2008-06-01 13:00 ` Russ Cox
2008-06-01 13:28 ` Enrico Weigelt
2008-06-01 14:26 ` Russ Cox [this message]
2008-06-01 15:41 ` erik quanstrom
2008-06-01 16:04 ` Eric Van Hensbergen
2008-06-04 3:23 ` erik quanstrom
2008-06-05 11:08 ` Enrico Weigelt
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=20080601142556.C91931E8C1F@holo.morphisms.net \
--to=rsc@swtch.com \
--cc=9fans@9fans.net \
--cc=weigelt@metux.de \
/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).