Xref: utzoo comp.protocols.nfs:1445 comp.unix.sysv386:1805
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!julius.cs.uiuc.edu!rpi!uupsi!sunic!chalmers.se!appli!niklas
From: niklas@appli.se (Niklas Hallqvist)
Newsgroups: comp.protocols.nfs,comp.unix.sysv386
Subject: NFS problem
Summary: How can I intercept 386/ix set file attributes remote procedure?
Keywords: NFS RPC attributes
Message-ID: <1178@appli.se>
Date: 3 Nov 90 00:08:07 GMT
Followup-To: comp.protocols.nfs
Organization: Applitron Datasystem AB, GOTHENBURG, SWEDEN
Lines: 29


	Hello NFS people!

About a month ago I posted the following article:
> 	I have a TCP/IP network with NFS on top of it.  Some of the
> nodes run Interactive 386/ix 2.0.1 (I think) who acts rather strangely
> when I try to set file attributes.  If some attributes are unspecified
> (e.g uid, gid or mode) they get changed anyway to -1.  I know this is
> mentioned in the NFS manual for 386/ix.  What I'm asking here is not
> why this happens, that I understand, but what to do about it.  Does
> someone know how to patch nfsd or nfs.o?  Have someone done a new
> version of the RP (remote procedure) which handles the set file attributes
> call?  Or maybe a RPC filter listening to the original NFS socket,
> forwarding some calls to a another port, after reconfiguring nfsd to
> listen this new port, and implementing new versions of other RPs.
> I'm interested in hints, partial or complete solutions to my problem.

I didn't get any answer and I saw no followups either.  The fact is: I'm not
the only one having this problem, there is at least one other site in
Sweden having the same difficulties (but in their case with 386/ix 2.2).
I plea, don't pass by this article if you got any ideas of what I can do.

				Thanks in advance,
				Niklas
-- 
Niklas Hallqvist	Phone: +46-(0)31-40 75 00
Applitron Datasystem	Fax:   +46-(0)31-83 39 50
Molndalsvagen 95	Email: niklas@appli.se
S-412 63  GOTEBORG, Sweden     mcsun!sunic!chalmers!appli!niklas