Date: Mon, 20 Oct 1997 00:21:00 +0900 (JST) From: sanpei@yy.cs.keio.ac.jp To: FreeBSD-gnats-submit@FreeBSD.ORG Subject: bin/4805: NFSv3 server readonly file permission problem Message-ID: <199710191521.AAA01031@fumi.yy.cs.keio.ac.jp> Resent-Message-ID: <199710191530.IAA13704@hub.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 4805 >Category: bin >Synopsis: NFSv3 server readonly file permission problem >Confidential: no >Severity: serious >Priority: medium >Responsible: freebsd-bugs >State: open >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Sun Oct 19 08:30:01 PDT 1997 >Last-Modified: >Originator: MIHIRA Yoshiro >Organization: Keio Univ. >Release: FreeBSD 2.2.5-971015-BETA i386 >Environment: NFSv3 server on FreeBSD 2.2(not tested on FreeBSD-current) and NFSv3 client. >Description: FreeBSD NFSv3 server has readonly file permission problem under xemacs and mule. I think this problem is from NFSv3 server file handle program. This problem is: o a file is managemented by RCS and still checked in. o If that file does not be checked out and is edited by emacs, o We can edit it and write it to NFSv3 server. There is no warning message. But I can't find out and fix it. >How-To-Repeat: 1. create readonly file on NFS server -r--r--r-- 1 sanpei yamamoto 1421 Oct 19 23:54 test 2. open test file by mule (also checked by xemacs) % mule -nw test 3. then.... case A [no problem] NFS server Solaris 2.5.1 for Intel NFS client FreeBSD 2.2.x and nfsv3 mount in minibuffer ``Note: file is write protected'' -- case B [no problem] NFS server FreeBSD 2.2.2-R NFS client FreeBSD 2.2.5-BETA and nfs**v2** mount in minibuffer ``Note: file is write protected'' -- case C [problem] NFS server FreeBSD 2.2.2-R NFS client FreeBSD 2.2.5-BETA and nfs**v3** mount open read/write mode and it can be editted and written by save-file. >Fix: Sorry I have no idea to solve it. >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199710191521.AAA01031>