Differences between current version and previous revision of ENODATA.
Other diffs: Previous Major Revision, Previous Author, or view the Annotated Edit History
Newer page: | version 3 | Last edited on Sunday, January 4, 2004 10:05:09 pm | by JohnMcPherson | |
Older page: | version 2 | Last edited on Sunday, January 4, 2004 10:58:10 am | by AnandBabu | Revert |
@@ -1,2 +1,8 @@
+!!!No data available
-66 #define
ENODATA 61 /
* No data available
*/
+It looks like this error condition is supposed to be used if a read(2) system call is used on a file descriptor in non-blocking mode and no data is ready to be read. However, according to the read(2) man page for the [GNU] [C] library, [EAGAIN] is used in this situation instead.
+
+
ENODATA is used in the linux kernel in a few places, however. For example:
+
* the [NTFS] and the [JFS] drivers use it as an error condition in a few places.
+* The "Intel CPU Microcode Update driver for Linux" uses this error code.
+
* The ftape driver returns this on an [ECC] read failure.