From b0fe68c13b04af8c098d53ea999bba6b7395163d Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 16 Sep 2020 12:04:55 +0000 Subject: Documentation fixes, by flexibeast --- doc/s6-fdholder-errorcodes.html | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'doc/s6-fdholder-errorcodes.html') diff --git a/doc/s6-fdholder-errorcodes.html b/doc/s6-fdholder-errorcodes.html index e082b7b..46add36 100644 --- a/doc/s6-fdholder-errorcodes.html +++ b/doc/s6-fdholder-errorcodes.html @@ -20,7 +20,7 @@

The following error messages (and corresponding -errno codes) +errno codes) can be returned by the s6-fdholderd daemon to its various clients. This page explains why they occur. @@ -32,7 +32,7 @@ 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. +usually been wiped out before an 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 @@ -47,7 +47,7 @@ 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 +RLIMIT_NOFILE resource limits used by the client and the server, and adjust them accordingly.
  • Resource busy (EBUSY): the client attempted to store -- cgit v1.3.1