aboutsummaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorPeter Seebach <peter.seebach@windriver.com>2013-02-27 14:26:25 -0600
committerPeter Seebach <peter.seebach@windriver.com>2013-02-27 14:26:25 -0600
commitb9eb2b5633b5a23efe72c950494728d93c2b5823 (patch)
treed17144fe7191c95748f730831ee0f8c4c0d9a3c8 /doc
parentd22e632f728c85fc4201bfeb069498afa073e823 (diff)
downloadpseudo-b9eb2b5633b5a23efe72c950494728d93c2b5823.tar.gz
pseudo-b9eb2b5633b5a23efe72c950494728d93c2b5823.tar.bz2
pseudo-b9eb2b5633b5a23efe72c950494728d93c2b5823.zip
documentation updates
Diffstat (limited to 'doc')
-rw-r--r--doc/pseudo_ipc21
1 files changed, 11 insertions, 10 deletions
diff --git a/doc/pseudo_ipc b/doc/pseudo_ipc
index 150a43e..0892bb7 100644
--- a/doc/pseudo_ipc
+++ b/doc/pseudo_ipc
@@ -35,16 +35,17 @@ is not thread-safe; this is part of (but not all of) the reason that there's
mutex stuff in the wrappers. (The other part is the "antimagic" being
able to blow things up.)
-type is one of PING, OP, SHUTDOWN, ACK, or NAK. The client only sends PING or
-OP. The server should always send ACK. When run with '-S', the pseudo
-program runs as a client, sending a SHUTDOWN message to a server -- but only
-if it can find one, it does not start a new one. In this case, the server
-could respond with a NAK, in which case it sends a message in which "path"
-is a list of space-separated PIDs of currently-living clients, for the program
-to print out in an error message. The server will not shut down while there
-are living clients. (The request, though, causes it to shut down immediately
-when there are no more clients, rather than waiting for the timeout
-period.)
+type is one of PING, OP, FASTOP, SHUTDOWN, ACK, or NAK. The client
+only sends PING, OP, or FASTOP. FASTOP takes no response, otherwise the
+server should always send ACK. When run with '-S', the pseudo program
+runs as a client, sending a SHUTDOWN message to a server -- but only if
+it can find one, it does not start a new one. In this case, the server
+could respond with a NAK, in which case it sends a message in which
+"path" is a list of space-separated PIDs of currently-living clients,
+for the program to print out in an error message. The server will
+not shut down while there are living clients. (The request, though,
+causes it to shut down immediately when there are no more clients,
+rather than waiting for the timeout period.)
result is the result of a particular operation. It applies only in replies
to OP messages.