c - When can such errors on bind() happen? -
errors taken man bind
enotsock // sockfd descriptor file, not socket. following errors specific unix domain (af_unix) sockets: efault // addr points outside user's accessible address space. eloop // many symbolic links encountered in resolving addr. enoent // file not exist. enotdir // component of path prefix not directory. erofs// socket inode reside on read-only file system.
especially can't understand when eloop, enoent, enotdir, erofs can happen. related special filesystems nfs , on?
remember sockets , bind
can used more network communication. see example unix domain sockets bound files in file system.
it's there in own quoted list of errors:
the following errors specific unix domain (af_unix) sockets
Comments
Post a Comment