+EXIT STATUS CODES
+
+For information about uservd's exit status, see uservd(8).
+
+The daemon's per-request children will note the success level of its
+request in its exit status. This will not usually be logged unless it
+is higher than those listed below; they are presented here for
+completeness and as programming documentation.
+
+ 2 - The connection was just an internal version check.
+
+ 4 - The client requested that the service be disconnected. This
+ includes normal termination, which is achieved by having the
+ server tell the client that the service has completed and waiting
+ for the client to tell it to disconnect.
+
+ 8 - The client closed its end of the socket when this would not
+ usually have been expected, causing an EPIPE or unexpected EOF in
+ the server. This is not an error condition - it can happen, for
+ example, if the client receives a fatal signal of some kind from
+ its execution environment (eg its controlling terminal).
+
+ 10 - The per-request child wishes the server to check whether it is
+ still the uservd.
+
+ 12 - The service failed onm the service side in an expected and
+ controlled manner, for example because it was rejected in the
+ configuration files.
+
+ 16 - A fatal system call failure or other general error occurred,
+ which ought not to have happened at all, barring system resource
+ shortages.
+
+ 20 - The client sent invalid data to the server, after the client
+ dropped all its system privilege. On some systems this can be
+ caused by a malicious calling user.
+
+ SIGABRT/SIGIOT - The client sent invalid data to the server before it
+ dropped all its system privileges, or some other unexpected
+ internal error occurred. This can also occur if an attempt to
+ block signals using sigprocmask fails.
+
+ 0-3,5-7,9,11,13-15,17-19 are not currently used by normal children.
+