From: "Gabriel Diaz" <gabidiaz@gmail.com>
To: "Alberto Cortés" <alcortes@it.uc3m.es>,
"Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] how to build a file server?
Date: Tue, 9 Jan 2007 18:59:21 +0100 [thread overview]
Message-ID: <82c890d00701090959w6c10cffk74e7df06fae70497@mail.gmail.com> (raw)
In-Reply-To: <20070109172558.GA4741@it.uc3m.es>
[-- Attachment #1: Type: text/plain, Size: 2465 bytes --]
Hello
the listen command you see should be run from the fossil console i think,
see fossilcons(8)
you can configure fossil using fossil/conf to run the listen command on each
boot
something like:
% fossil/conf /dev/sdC0 > flproto
add listen command to flproto
% cat flproto | fossil/conf -w /dev/sdC0
check the fossil man pages for the correct syntax.
slds.
gabi
On 1/9/07, Alberto Cortés <alcortes@it.uc3m.es> wrote:
>
> I have a cpu/auth/fs server configured as the Wiki
> ("Configuring_a_Standalone_CPU_Server") suggests. I have created
> some test user accounts.
>
> I also have an standalone terminal (with its own fossil).
>
> I can cpu from the terminal to the server (as any user).
> I can drawterm to the server (as any user).
>
> My problem(s):
> I can not boot the terminal with the server as fs and auth:
> (boot: can't connect to file server: connection timed out)
> Also, I can not 9fs to the server.
>
>
>
> Running "snoopy" and "netstat -n" on the server I have discovered
> that my server is not a fs server at all. There is nobody
> listening at tcp 564.
>
> /rc/bin/service/!tcp564 launch exportfs which I belive is not
> authenticated: if I rename /rc/bin/service/!tcp564 to
> /rc/bin/service/tcp564 and reboot the server, my problem is
> gone, I can 9fs to it and boot the terminal with the server
> as fs and auth. But the user is not asked for a password when
> booting :(.
>
> Searching 9fans archive I have read that:
>
> disk/kfscmd 'listen tcp!*!564'
>
> is this solutions to all my problems.
>
> Also on the wiki (Setting_up_fossil) says:
>
> If you want to serve the network you can run the commands
>
> listen tcp!*!9fs
> listen il!*!9fs
>
>
> but there are some things in kfscmd manpage that I don't fully
> ubnderstands and prevent me from using the "disk/kfscmd" solution:
>
> listen [address]
>
> [...]
> This feature is intended to facilitate small
> networks of a couple machines in the situation when
> convenience is more important than performance. This
> command is only useful on machines with (possibly
> simulated) NVRAM, which needs to be readable to the kfs
> processes; see readnvram in authsrv(2). The production
> file server (see fs(4)) is strongly encouraged for
> anything more than casual use.
> [...]
>
> So, how do I properly build a file server?
>
>
> --
> http://bach.gast.it.uc3m.es/~alcortes/index.html
>
[-- Attachment #2: Type: text/html, Size: 3548 bytes --]
next prev parent reply other threads:[~2007-01-09 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-09 17:25 Alberto Cortés
2007-01-09 17:59 ` Gabriel Diaz [this message]
2007-01-09 19:01 ` Gorka guardiola
2007-01-09 19:07 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=82c890d00701090959w6c10cffk74e7df06fae70497@mail.gmail.com \
--to=gabidiaz@gmail.com \
--cc=9fans@cse.psu.edu \
--cc=alcortes@it.uc3m.es \
/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).