server/: Augment challenges to allow a payload.

[tripe] / server / tripe-admin.5.in

diff --git a/server/tripe-admin.5.in b/server/tripe-admin.5.in
index af6c97a..5836eea 100644 (file)
--- a/server/tripe-admin.5.in
+++ b/server/tripe-admin.5.in
@@ -1030,6 +1030,17 @@ There is already a peer named
 The attempt to send a ping packet failed, probably due to lack of
 encryption keys.
 .SP
 The attempt to send a ping packet failed, probably due to lack of
 encryption keys.
 .SP

+.B "provider-failed"
+(For
+.BR SVCSUBMIT .)
+The service provider disconnected without sending back a final reply to
+the job.
+.SP
+.B "provider-overloaded"
+(For
+.BR SVCSUBMIT .)
+The service provider has too many jobs queued up for it already.
+.SP

 .BI "resolve-error " hostname
 (For
 .BR ADD .)
 .BI "resolve-error " hostname
 (For
 .BR ADD .)


@@ -1102,7 +1113,7 @@ The port name
 .I port
 couldn't be found in
 .BR /etc/services .
 .I port
 couldn't be found in
 .BR /etc/services .

-.TP
+.SP

 .BI "unknown-service " service
 (For
 .BR SVCENSURE ,
 .BI "unknown-service " service
 (For
 .BR SVCENSURE ,


@@ -1113,7 +1124,7 @@ and
 The token
 .I service
 is not recognized as the name of a client-provided service.
 The token
 .I service
 is not recognized as the name of a client-provided service.

-.TP
+.SP

 .BI "unknown-tag " tag
 (For
 .BR BGCANCEL .)
 .BI "unknown-tag " tag
 (For
 .BR BGCANCEL .)


@@ -1121,6 +1132,13 @@ The given
 .I tag
 is not the tag for any outstanding background job.  It may have just
 finished.
 .I tag
 is not the tag for any outstanding background job.  It may have just
 finished.

+.SP
+.BI "unknown-tunnel " tun
+(For
+.BR ADD .)
+The given
+.I tun
+is not the name of any known tunnel driver.

 .
 .\"--------------------------------------------------------------------------
 .SH "NOTIFICATIONS"
 .
 .\"--------------------------------------------------------------------------
 .SH "NOTIFICATIONS"


@@ -1520,6 +1538,51 @@ The peer (apparently) sent a transport ping response whose id doesn't
 match any outstanding ping.  Maybe it was delayed for longer than the
 server was willing to wait, or maybe the peer has gone mad; or maybe
 there are bad people trying to confuse you.
 match any outstanding ping.  Maybe it was delayed for longer than the
 server was willing to wait, or maybe the peer has gone mad; or maybe
 there are bad people trying to confuse you.

+.SS "PRIVSEP warnings"
+These indicate problems with the privilege-separation helper process.
+(The server tries to drop its privileges when it starts up, leaving a
+privileged helper process behind which will create and hand over tunnel
+descriptors on request, but hopefully not do anything else especially
+dangerous.  Tunnel descriptors are not completely safe, but this is
+probably better than nothing.)
+.SP
+.BI "PRIVSEP child-exited " rc
+The helper process exited normally with status
+.IR rc .
+Status 0 means that it thought the server didn't want it any more; 1
+means that it was invoked incorrectly; 127 means that some system call
+failed.
+.SP
+.BI "PRIVSEP child-killed " sig
+The helper process was killed by signal number
+.IR sig .
+.SP
+.BI "PRIVSEP child-died " status
+The helper process died in some unexpected way;
+.I status is the raw status code returned by
+.BR waitpid (2),
+because the server didn't understand how to decode it.
+.SP
+.BI "PRIVSEP helper-died"
+A tunnel driver requires a tunnel descriptor from the helper, but the
+helper isn't running so this won't work.
+.SP
+.BI "PRIVSEP helper-read-error " ecode " " message
+The server failed to read a response from the helper process.
+.SP
+.BI "PRIVSEP helper-short-read"
+The helper process didn't send back enough data, and has likely crashed.
+.SP
+.BI "PRIVSEP helper-write-error " ecode " " message
+The server failed to send a message to the helper process.
+.SP
+.BI "PRIVSEP no-fd-from-helper"
+The helper process sent back a positive response, but didn't include the
+requested tunnel descriptor.
+.SP
+.BI "PRIVSEP unknown-response-code"
+The helper process sent back an incomprehensible reply.  It's probably
+very confused and may crash.

 .SS "SERVER warnings"
 These indicate problems concerning the server process as a whole.
 .SP
 .SS "SERVER warnings"
 These indicate problems concerning the server process as a whole.
 .SP


@@ -1551,6 +1614,10 @@ option), and encountered end-of-file on standard input.
 .BI "SERVER select-error " ecode " " message
 An error occurred in the server's main event loop.  This is bad: if it
 happens too many times, the server will abort.
 .BI "SERVER select-error " ecode " " message
 An error occurred in the server's main event loop.  This is bad: if it
 happens too many times, the server will abort.

+.SP
+.BI "SERVER waitpid-error " ecode " " message
+The server was informed that one of its child processes had exited, but
+couldn't retrieve the child's status.

 .SS "SYMM warnings"
 These are concerned with the symmetric encryption and decryption
 process.
 .SS "SYMM warnings"
 These are concerned with the symmetric encryption and decryption
 process.