[PATCH.HURD] fix fdatasync/fsync if file_sync is not supported

Samuel Thibault samuel.thibault@gnu.org
Thu Oct 25 17:47:00 GMT 2012

Previous message (by thread): [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported
Next message (by thread): [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Roland McGrath, le Thu 25 Oct 2012 09:49:51 -0700, a Ã©crit :
> We don't generally handle MIG_BAD_ID.  That error indicates a server not
> implementing the protocol for which it's being used, which is a server bug.

Pino, in which case did you actually get MIG_BAD_ID precisely?

Samuel

Previous message (by thread): [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported
Next message (by thread): [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

More information about the Libc-alpha mailing list