From 8bffa1c19fd05f4f04dad4b5b98f85b94f23113c Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Mon, 26 Jan 2015 22:26:57 +0000 Subject: - added s6-fdholder-delete(c) - small s6-fdholder-* fixes - s6-fdholder documentation (in review) - s6_svstatus_* bugfix (thanks Olivier Brunel) --- doc/s6-fdholder-errorcodes.html | 72 +++++++++++++++++++++++++++++++++++++++++ 1 file changed, 72 insertions(+) create mode 100644 doc/s6-fdholder-errorcodes.html (limited to 'doc/s6-fdholder-errorcodes.html') diff --git a/doc/s6-fdholder-errorcodes.html b/doc/s6-fdholder-errorcodes.html new file mode 100644 index 0000000..8e41365 --- /dev/null +++ b/doc/s6-fdholder-errorcodes.html @@ -0,0 +1,72 @@ + + + + + s6: the s6-fdholder error codes + + + + + + +

+s6
+Software
+skarnet.org +

+ +

The `s6-fdholder` error codes

+ +

+ The following error messages (and corresponding +errno codes) +can be returned by the +s6-fdholderd daemon to its various clients. +This page explains why they occur. +

+ +

Protocol error (EPROTO) or Protocol wrong type +for socket (EPROTOTYPE): the client connected to the wrong +kind of server and they cannot communicate. This is generally a +programming error. It can also +signal a bug in the s6-fdholder tools, but protocol bugs have +usually been wiped out before a s6 release.
Broken pipe (EPIPE): the client was not authorized to +connect to the server, which closed the connection. You need to +configure the access +rights to the server.
Operation not permitted (EPERM): even though the +client was authorized to connect to the server, the specific +operation it wanted to perform was denied. You need to +configure the access +rights to the server.
Too many open files in system (ENFILE): the client +attempted to store more file descriptors than the server can hold. +Or, the client attempted to retrieve more file descriptors than it +can hold. You should check the -n option to +s6-fdholderd, as well as the +RLIMIT_NOFILE +resource limits used by the client and the server, and adjust them +accordingly.
Resource busy (EBUSY): the client attempted to store +a descriptor under an identifier that is already used.
Filename too long (ENAMETOOLONG): the identifier +provided by the client was too long.
No such file or directory (ENOENT): the identifier +provided by the client was not found in the server database.
Bad file descriptor (EBADF): the client attempted +to transmit a closed, or otherwise unsuitable for fd-passing, +file descriptor.
Operation timed out (ETIMEDOUT): the client, or the +server, took too long to perform the wanted operation. This is most +probably a programming error, because both client and server should +have a very fast reaction time. Check that the client is connecting +to the right server, and check -t options to both client and +server (the argument is interpreted as milliseconds!).
Other errors indicate a transient error such as lack of memory, +hardware failure, etc.

+ + + -- cgit v1.3.1

The s6-fdholder error codes

The `s6-fdholder` error codes