9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Russ Cox" <rsc@swtch.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9nfs
Date: Thu,  9 Oct 2003 20:10:09 -0400	[thread overview]
Message-ID: <E1A7krB-000Mj8-B0@t40.swtch.com> (raw)
In-Reply-To: Your message of "Fri, 10 Oct 2003 02:38:52 BST." <344e0ec7b586b08b5df68b7b3843b1dd@juice.thebigchoice.com>

> Before I start the long journey does anyone have any insight into how
> well plan9 behaves as an nfs server.

Behavior is adequate, but not spectacular.  I have an NFS3 server
somewhere, but it's not any faster.  It might be more stable.
Without locking support, I'm not sure you'll be able to
boot FreeBSD off it.

I've used it to serve NFS to Linux and FreeBSD before,
but the lack of exact Unix semantics (in particular the
locking) usually forces me to store the files on the
alien systems and use u9fs.

> =============
> 		free(m);
> 		break;
> 	}
> fprint(2, "looking for %lux\n", clientip);
> 	if(getdom(clientip, dom, sizeof dom)<0){
> 		clog("auth: unknown ip address");
> 		return nil;
> 	}
> fprint(2, "dom is %s\n", dom);
> 	for(r=idhead; r; r=r->next){
> 		if(r->u.timestamp == 0 || r->g.timestamp == 0)
> ==========

This I always have problems with -- the clients must
be listed in ndb in order to be spoken to, so these
prints tell me what's going on.

> ==========
>
> 	char *l;
> // 	long savalarm;
>
> // 	savalarm = alarm(0);
> 	in = Bopen(file, OREAD);
> 	if(in == 0){
> 		clog("readunixidmaps can't open %s: %r\n", file);
> //		alarm(savalarm);
> 		return -1;
> 	}
> ===============

This caused problems for Geoff.  The alarm can interrupt
other I/O and confuse things.  I don't remember the details.

Russ


  reply	other threads:[~2003-10-10  0:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-10  1:38 matt
2003-10-10  0:10 ` Russ Cox [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-10-10  0:54 YAMANASHI Takeshi

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=E1A7krB-000Mj8-B0@t40.swtch.com \
    --to=rsc@swtch.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).