From: mirtchov@cpsc.ucalgary.ca
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9p srv-ing on a port
Date: Fri, 16 Jan 2004 17:40:03 -0700 [thread overview]
Message-ID: <ccfa273ec0ee54fb6c533db5660e9290@plan9.ucalgary.ca> (raw)
In-Reply-To: <cd9922c13e490c570678ed5a1f0bdde4@plan9.bell-labs.com>
> What is the real question?
Skip's answer will probably suffice.
Originally I wanted to have a threaded server listen to a port on
which many clients can connect, similar to what fossil and kfs are
doing on 17008. Clients do:
srv tcp!somesuch!someport blah /mnt/blah
and that's all...
Initially I thought it may be enough to build a Tree structure proper
and run srv() on it by setting (Srv *)s->infd and (Srv)s->outfd to be
the file descriptor obtained by accept(), but that doesn't seem to be
the case.
I admit I haven't dug through other servers' sources too deeply.
Something else I'm interested in doing is having a /srv (or a similar
fs alternative) on which remote machines can post file descriptors to
parts of their namespace. A srvfs that will post on a remote machine
in other words. Just to make sure that the trivial way doesn't work,
I tried:
home% import -c octarine /srv /srv
home% srvfs tmp /tmp
exportfs: can't read initial string:
home% mount /srv/tmp /n/sources
mount: can't open /srv/tmp: device shut down
home%
Anyway, there's no excuse for not digging in deeper, except perhaps
that it's Friday :)
andrey
next prev parent reply other threads:[~2004-01-17 0:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-16 23:06 mirtchov
2004-01-17 0:17 ` David Presotto
2004-01-17 0:40 ` mirtchov [this message]
2004-01-17 0:56 ` Skip Tavakkolian
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=ccfa273ec0ee54fb6c533db5660e9290@plan9.ucalgary.ca \
--to=mirtchov@cpsc.ucalgary.ca \
--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).