`
arksea
  • 浏览: 63746 次
  • 性别: Icon_minigender_1
  • 来自: 福州
社区版块
存档分类
最新评论

POSIX错误码对照表

阅读更多

在module:file、inet等模块里可以找到,经常会忘记,在此记录以备查

file:

  • eacces - permission denied
  • eagain - resource temporarily unavailable
  • ebadf - bad file number
  • ebusy - file busy
  • edquot - disk quota exceeded
  • eexist - file already exists
  • efault - bad address in system call argument
  • efbig - file too large
  • eintr - interrupted system call
  • einval - invalid argument
  • eio - IO error
  • eisdir - illegal operation on a directory
  • eloop - too many levels of symbolic links
  • emfile - too many open files
  • emlink - too many links
  • enametoolong - file name too long
  • enfile - file table overflow
  • enodev - no such device
  • enoent - no such file or directory
  • enomem - not enough memory
  • enospc - no space left on device
  • enotblk - block device required
  • enotdir - not a directory
  • enotsup - operation not supported
  • enxio - no such device or address
  • eperm - not owner
  • epipe - broken pipe
  • erofs - read-only file system
  • espipe - invalid seek
  • esrch - no such process
  • estale - stale remote file handle
  • exdev - cross-domain link

inet:

  • e2big - argument list too long
  • eacces - permission denied
  • eaddrinuse - address already in use
  • eaddrnotavail - cannot assign requested address
  • eadv - advertise error
  • eafnosupport - address family not supported by protocol family
  • eagain - resource temporarily unavailable
  • ealign - EALIGN
  • ealready - operation already in progress
  • ebade - bad exchange descriptor
  • ebadf - bad file number
  • ebadfd - file descriptor in bad state
  • ebadmsg - not a data message
  • ebadr - bad request descriptor
  • ebadrpc - RPC structure is bad
  • ebadrqc - bad request code
  • ebadslt - invalid slot
  • ebfont - bad font file format
  • ebusy - file busy
  • echild - no children
  • echrng - channel number out of range
  • ecomm - communication error on send
  • econnaborted - software caused connection abort
  • econnrefused - connection refused
  • econnreset - connection reset by peer
  • edeadlk - resource deadlock avoided
  • edeadlock - resource deadlock avoided
  • edestaddrreq - destination address required
  • edirty - mounting a dirty fs w/o force
  • edom - math argument out of range
  • edotdot - cross mount point
  • edquot - disk quota exceeded
  • eduppkg - duplicate package name
  • eexist - file already exists
  • efault - bad address in system call argument
  • efbig - file too large
  • ehostdown - host is down
  • ehostunreach - host is unreachable
  • eidrm - identifier removed
  • einit - initialization error
  • einprogress - operation now in progress
  • eintr - interrupted system call
  • einval - invalid argument
  • eio - I/O error
  • eisconn - socket is already connected
  • eisdir - illegal operation on a directory
  • eisnam - is a named file
  • el2hlt - level 2 halted
  • el2nsync - level 2 not synchronized
  • el3hlt - level 3 halted
  • el3rst - level 3 reset
  • elbin - ELBIN
  • elibacc - cannot access a needed shared library
  • elibbad - accessing a corrupted shared library
  • elibexec - cannot exec a shared library directly
  • elibmax - attempting to link in more shared libraries than system limit
  • elibscn - .lib section in a.out corrupted
  • elnrng - link number out of range
  • eloop - too many levels of symbolic links
  • emfile - too many open files
  • emlink - too many links
  • emsgsize - message too long
  • emultihop - multihop attempted
  • enametoolong - file name too long
  • enavail - not available
  • enet - ENET
  • enetdown - network is down
  • enetreset - network dropped connection on reset
  • enetunreach - network is unreachable
  • enfile - file table overflow
  • enoano - anode table overflow
  • enobufs - no buffer space available
  • enocsi - no CSI structure available
  • enodata - no data available
  • enodev - no such device
  • enoent - no such file or directory
  • enoexec - exec format error
  • enolck - no locks available
  • enolink - link has be severed
  • enomem - not enough memory
  • enomsg - no message of desired type
  • enonet - machine is not on the network
  • enopkg - package not installed
  • enoprotoopt - bad proocol option
  • enospc - no space left on device
  • enosr - out of stream resources or not a stream device
  • enosym - unresolved symbol name
  • enosys - function not implemented
  • enotblk - block device required
  • enotconn - socket is not connected
  • enotdir - not a directory
  • enotempty - directory not empty
  • enotnam - not a named file
  • enotsock - socket operation on non-socket
  • enotsup - operation not supported
  • enotty - inappropriate device for ioctl
  • enotuniq - name not unique on network
  • enxio - no such device or address
  • eopnotsupp - operation not supported on socket
  • eperm - not owner
  • epfnosupport - protocol family not supported
  • epipe - broken pipe
  • eproclim - too many processes
  • eprocunavail - bad procedure for program
  • eprogmismatch - program version wrong
  • eprogunavail - RPC program not available
  • eproto - protocol error
  • eprotonosupport - protocol not supported
  • eprototype - protocol wrong type for socket
  • erange - math result unrepresentable
  • erefused - EREFUSED
  • eremchg - remote address changed
  • eremdev - remote device
  • eremote - pathname hit remote file system
  • eremoteio - remote i/o error
  • eremoterelease - EREMOTERELEASE
  • erofs - read-only file system
  • erpcmismatch - RPC version is wrong
  • erremote - object is remote
  • eshutdown - cannot send after socket shutdown
  • esocktnosupport - socket type not supported
  • espipe - invalid seek
  • esrch - no such process
  • esrmnt - srmount error
  • estale - stale remote file handle
  • esuccess - Error 0
  • etime - timer expired
  • etimedout - connection timed out
  • etoomanyrefs - too many references
  • etxtbsy - text file or pseudo-device busy
  • euclean - structure needs cleaning
  • eunatch - protocol driver not attached
  • eusers - too many users
  • eversion - version mismatch
  • ewouldblock - operation would block
  • exdev - cross-domain link
  • exfull - message tables full
  • nxdomain - the hostname or domain name could not be found
  •  

    分享到:
    评论

    相关推荐

      posix官方相关文档

      POSIX Base Definitions.pdf POSIX Base Specifications, Issue 7.pdf POSIX Rationale (Informative).pdf POSIX Realtime and Embedded Application Support.pdf(IEEE std 1003.13-2003) POSIX Shell and ...

      POSIX标准以及函数接口查询

      5. **错误处理**:当系统调用失败时,`errno`全局变量会记录错误代码,`perror()`函数可以将这个代码转换为易于理解的错误消息。 6. **时间和日期**:POSIX提供了`time()`、`ctime()`、`difftime()`等函数来处理...

      Posix(1).rar_POSIX Pthread_posix_pthread_pthread posix

      8. **错误处理**:pthreads API通常返回错误代码,如`EINVAL`(无效参数)或`EBUSY`(资源忙),需要正确处理这些错误以确保程序的健壮性。 9. **示例代码**:指南中可能包含实际的代码示例,演示如何在实际项目中...

      POSIX 官方正式 标准 (内含8个文档)

      POSIX Base Definitions;POSIX Base Specifications, Issue 7;POSIX Rationale (Informative);POSIX® Realtime and Emeded Application Support;POSIX® Shell and Utilities;POSIX System Interfaces;POSIX ...

      Posix标准接口文档(英文版).pdf

      POSIX(Portable Operating System Interface)标准是一套定义了操作系统接口的国际标准,旨在提供一个统一的、跨平台的编程环境,使软件可以在多种操作系统上运行,而无需进行大量的修改。这个标准由IEEE(电气和...

      并行计算 + Posix

      4. **Posix信号**:介绍如何使用信号进行进程间的通信和错误处理,如SIGINT、SIGTERM和SIGKILL等。 5. **Posix时间与定时器**:讲解时间相关的函数(如time、sleep、alarm、clock_gettime等),以及如何使用定时器...

      POSIX1003标准文档

      8. **错误处理**:定义了统一的错误代码和错误处理机制,以确保程序在面对各种错误情况时的行为一致。 9. **国际化和本地化**:规定了如何处理多语言环境,包括字符集转换和文本排序规则。 10. **安全性和认证**:...

      POSIX-C.rar

      9. **错误处理**:POSIX标准规定了错误码系统,通过`errno`全局变量记录错误信息,方便开发者调试和定位问题。 10. **内存管理**:虽然C语言自身提供了内存分配和释放的函数,如`malloc()`、`free()`,但POSIX还...

      Micrium_POSIX.tar_feeloru_rtos_Micrium_POSIX_

      通过这种移植,开发者可以编写一次代码,然后在多个平台上运行,无需进行大量修改,极大地提高了软件的可移植性和复用性。 在Micrium的实现中,POSIX接口被适配到其RTOS内核,如uC/OS。这个内核以其小巧、高效著称...

      POSIX规范多线程代码示例

      在这个名为"POSIX规范多线程代码示例"的压缩包中,你将找到六个使用C++的POSIX线程库(pthread)编写的示例,它们逐步展示了如何在Linux和Windows环境下(使用Visual Studio,需添加-lpthread链接选项)创建和管理多...

      POSIX多线程程序设计.pdf

      此外,本书还讨论了调度的问题,并给出了避免错误和提高性能等问题的有价值的建议。本书使用了大量注释过后 实例来解释实际的概念,并包括Pthreads的简单索引和对标准化的展望。 《POSIX多线程程序设计》适合有经验...

      POSIX最新标准文档

      这些规范覆盖了进程管理、文件操作、网络通信、信号处理、时间与定时、错误处理等多个方面,确保开发者可以在符合POSIX标准的系统上编写可移植的代码。 在提供的压缩包文件中,我们看到几个关键文件名: 1. `susv3...

      posix 接口 入门资料

      POSIX(Portable Operating System Interface)接口是一套标准,旨在确保不同UNIX系统间的源代码可移植性。这个入门资料集合包含了多个资源,可以帮助你深入理解和掌握POSIX接口在UNIX和类UNIX系统,如Linux中的应用...

      POSIX 1003.1-2004

      这些函数使得开发者可以在不依赖特定操作系统的情况下编写代码,提高了代码的可移植性。 其次,Shell命令语言部分规定了如何通过命令行与操作系统进行交互,比如ls、cd、rm等常用命令。这些命令的语法和行为在符合...

      最新版免费 POSIX 标准文档

      最新版免费 POSIX 标准文档,下载即用.POSIX表示可移植操作系统接口(Portable Operating System Interface of UNIX,缩写为 POSIX ),POSIX标准定义了操作系统应该为应用程序提供的接口标准,是IEEE为要在各种UNIX...

      posix协议标准总体分析

      例如,`errno`全局变量用于存储函数调用的错误代码,`<sys/types.h>`头文件定义了如`dev_t`、`ino_t`等数据类型,而`environ`指向进程执行时的环境变量数组。 3. **接口和设备**:包括了文件系统、进程、信号、...

      前端开源库-posix

      5. **其他系统服务**:库还可能包括时间管理、错误处理、权限管理等功能,让前端开发者能够以更符合他们服务器端经验的方式编写代码。 使用"前端开源库-posix",开发者可以利用其提供的API,以统一的编程风格处理...

      posix接口学习资料

      学习这些资料,你将能够掌握如何在遵循POSIX标准的系统上编写高效、可移植的代码。UNIX环境高级编程将帮你理解操作系统的工作原理,POSIX.CHM会提供API的详细信息,Linux多线程编程.doc将引导你进入并发编程的世界,...

      posix 多线程程序设计

      通过使用POSIX线程,开发者可以在同一进程中创建多个执行单元(线程),每个线程可以独立执行代码,从而实现并发处理,提高系统的响应能力和处理速度。 ### 多线程编程的重要性 多线程编程在现代计算环境中至关...

      8_posix_signal

      这个“8_posix_signal”压缩包文件很可能包含了与实现POSIX信号相关的代码示例,可能来源于CSDN博主shallnet的一篇博客文章的源代码。 首先,我们来详细了解一下POSIX信号的基本概念。POSIX信号是操作系统向进程...

    Global site tag (gtag.js) - Google Analytics