From mboxrd@z Thu Jan  1 00:00:00 1970
To: 9fans@cse.psu.edu
Subject: Re: [9fans] 9nfs
In-Reply-To: Your message of "Fri, 10 Oct 2003 02:38:52 BST."
             <344e0ec7b586b08b5df68b7b3843b1dd@juice.thebigchoice.com>
From: "Russ Cox" <rsc@swtch.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-ID: <87364.1065744609.1@t40.swtch.com>
Message-Id: <E1A7krB-000Mj8-B0@t40.swtch.com>
Date: Thu,  9 Oct 2003 20:10:09 -0400
Topicbox-Message-UUID: 6b406eb6-eacc-11e9-9e20-41e7f4b1d025

> 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