lkml.org 
[lkml]   [1999]   [Nov]   [30]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: linux nfs client problem
Date
> > then this will fail on more than one NFS implementation.
> Said nfs CLIENT implementations are broken.
> By design, the UNIX file system checks file access permissions with
> OPEN, not WRITE.

NFS is not posix compliant.

> In order to implement this over NFS, client WRITE operations must
> use the credentials from OPEN not not the credentials the process
> has at the time of WRITE.

That would be a good idea. Its certainly on the list of things wrong with
the old NFS client code. I'm not sure what the status on this is.

However relying on this behaviour is also wrong. In fact the whole idea of
standard unix permissions is not required NFS just normal NFS. Most people
tend to use procmail to do NFS deliveries. It handles locking/flushing
issues nicely. It knows that close() can return an error which is something
most apps get wrong over NFS.

As a fix I'd suggest you tell it to use procmail as your delivery agent.
I would think postfix is capable of this as I've yet to meet a good mailer
that isnt.

Alan


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/

\
 
 \ /
  Last update: 2005-03-22 13:55    [W:0.022 / U:0.248 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site