[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported
From: |
Roland McGrath |
Subject: |
Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported |
Date: |
Fri, 26 Oct 2012 11:22:46 -0700 (PDT) |
> AIUI, POSIX says there can be other, implementation-defined errors.
That's true. But when POSIX specifies a particular error code for a
particular condition, then you must yield the specified error code for that
situation. If this is arising for something like using a file-oriented
call on an fd that is a socket or pipe (i.e. something that any program
could do on any POSIX system) then it really should result in the expected
POSIX error code.
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Pino Toscano, 2012/10/24
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Roland McGrath, 2012/10/25
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Samuel Thibault, 2012/10/25
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Svante Signell, 2012/10/26
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Samuel Thibault, 2012/10/26
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Pino Toscano, 2012/10/26
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Samuel Thibault, 2012/10/26
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Richard Braun, 2012/10/26
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Samuel Thibault, 2012/10/26
- Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported,
Roland McGrath <=
Re: [PATCH.HURD] fix fdatasync/fsync if file_sync is not supported, Pino Toscano, 2012/10/29