Commit b2c23b8f authored by Per Cederqvist's avatar Per Cederqvist
Browse files

Doc fixes.

parent ddc9668a
......@@ -27,7 +27,7 @@
# - first, a socket bound to a specific port. This lock ensures
# that only a single test is run on this computer. If two tests
# were run at the same time, they would interfere with each other,
# since static port is used by the test suite.
# since a static port is used by the test suite.
#
# - secondly, a symlink in the current working directory, that
# points to the host and pid of this process. This lock ensures
......@@ -36,7 +36,7 @@
#
# This process communicates with the test suite on stdin/stdout.
# It understands a single command: "exit\n". It can send these
# responses:
# status messages:
#
# "locking...\n": this is sent as soon as the process is started.
#
......@@ -52,11 +52,11 @@
# full path to the symlink lock file, $HOST replaced by the host
# name and $PID by the pid of the process holding the lock. This
# message may be issued several times, but never with the same
# values of bot $HOST and $PID.
# values of both $HOST and $PID.
#
# "failed: file $LOCK $HOST $PID\n": the symlink lock may be a stale
# lock. If $HOST is the local host, the program can check for
# stale locks and break them. However, it it is held by a remote
# stale locks and break them. However, if it is held by a remote
# host, that isn't possible. After waiting an hour for a lock
# that is still held by the same remote host and pid, this program
# will print this message and stop trying to obtain the lock. If
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment