Jeff Victor <[EMAIL PROTECTED]> wrote:
> >>Your working did not match with the reality, this is why I did write this.
> >>You did write that upon close() the client will first do something similar
> >>to
> >>fsync on that file. The problem is that this is done asynchronously and the
> >>close() return value does noo contain an indication on whether the fsync
> >>did succeed.
> >
> > Sorry, the code in Solaris would behave as I described. Upon the
> > application closing the file, modified data is written to the server.
> > The client waits for completion of those writes. If there is an error,
> > it is returned to the caller of close().
>
> Are you talking about the client-end of NFS, as implemented in Solaris, or
> the
> "application-clients" like vi?
>
> It seems to me that you are talking about Solaris, and Joerg is talking about
> vi
> (and other applications).
I am talking about the syscall interface to applications.
Jörg
--
EMail:[EMAIL PROTECTED] (home) Jörg Schilling D-13353 Berlin
[EMAIL PROTECTED] (uni)
[EMAIL PROTECTED] (work) Blog: http://schily.blogspot.com/
URL: http://cdrecord.berlios.de/old/private/ ftp://ftp.berlios.de/pub/schily
_______________________________________________
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
