I don't know, the Java guys are pretty good about making sure their API works consistently across all platforms, or at least documenting the cases where it wouldn't.

I would start with a read only descriptor and get it into the field.

You could always have a runtime property that controller using read or write descriptors.

On Nov 30, 2007, at 12:09 PM, Yonik Seeley wrote:

On Nov 30, 2007 12:42 PM, robert engels <[EMAIL PROTECTED]> wrote:
It is unclear if you need to open them for writing. The unix specs
clearly allow you do call fsync on ANY file descriptor.

The Linux docs seem to imply that a file descriptor opened for write
is required.

The Java specification allows it on ANY file descriptor as well -
this should be the only one that matters.

AIX docs say that fd opened for write is required... one of the error codes is
 "EBADF     The FileDescriptor parameter is not a valid file descriptor
open for writing."

Java can't do much if the underlying OS doesn't support it, so it
looks like we need to open for writing to sync.

-Yonik

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to