Note somewhat-experimental nature of syslog.

Note that BREAK-DOT-LOCK does not necessarily remove a lock for good.

doc/scsh-manual/miscprocs.tex

@@ -94,7 +94,11 @@ Here is scsh's interface to dot-locking:
 \defun {break-dot-lock} {file-name} {undefined}
 
 \begin{desc}
-  Breaks the lock for \var{file-name} if one exists.
+  Breaks the lock for \var{file-name} if one exists.  Note that
+  breaking a lock does \emph{not} imply a subsequent
+  \ex{obtain-dot-lock} will succeed, as another party may have
+  acquired the lock between \ex{break-dot-lock} and
+  \ex{obtain-dot-lock}.
 \end{desc}
 
 \defun {release-dot-lock} {file-name} {\boolean}
@@ -124,6 +128,9 @@ Here is scsh's interface to dot-locking:
 \section{Syslog facility}
 \label{syslog-facility}
 
+(Note: the functionality presented in this section is still somewhat
+experimental and thus subject to interface changes.)
+
 The procedures in this section provide access to the 4.2BSD syslog
 facility present in most POSIX systems.  The functionality is in a
 structure called \ex{syslog}.  There's an additional structure