🚀 go-pugleaf

Hi,

I know people asking questions here should be able to write Unix from
scratch, but I'll ask you a question anyway :-) (I think it requires
some wizardry knowledge)

I'm writting an nfs front end to a database, but first I am testing
the basic functions by just mirroring a regular ufs through my own
nfsd.

Sytem used:
	Sparcstation with SunOS4.1.1

The server:
	It listens to port 2048, and it does not register itself to 
	the portmapper;
	It is based on NFS Protocol version 2

Client Side:
	I have written a mount command that does a mount system call.
	This allows me to use a port that is different from the standard
	nfs port, and thus have my own server cohexist with standard NFS.

1. Now, after mounting the filesystem, I do an ls -R and I get
everything listed. I can see the server processing nfs_getattr,
nfs_readdir and nfs_lookup calls and everything runs as expected.

2. If I issue the ls command a second time, the only call that the
server will have to serve is a single call to nfs_getattr.

3. If I do a touch on the mountpoint, then I essentially am back to 1
when I do an ls command, otherwise I'm stuck in the situation 2.

This is if my nfs_getattr gives the time(atime,mtime,ctime) that the
physical file has.

However, things work as expected when I cheat and use the current time
(as returned by time(3)) for the value of mtime, except for the fact
that mtime is not what it should be.

Why is this?

Any help will be  greatly appreciated.

Thanks in advance.

BTW, if you don't think it is an interesting question, then maybe you
should just answer to me by e-mail.
--
  ,
Stephane Boucher | Bell-Northern Research
sbo@bnr.ca