From b0fe68c13b04af8c098d53ea999bba6b7395163d Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Wed, 16 Sep 2020 12:04:55 +0000 Subject: Documentation fixes, by flexibeast --- doc/libs6/s6lockd.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'doc/libs6/s6lockd.html') diff --git a/doc/libs6/s6lockd.html b/doc/libs6/s6lockd.html index 9fcb055..089de57 100644 --- a/doc/libs6/s6lockd.html +++ b/doc/libs6/s6lockd.html @@ -39,11 +39,11 @@ user: it will be spawned by the
  1. Use the s6lock_startf() library call. -A s6lockd child will then be spawned from your +An s6lockd child will then be spawned from your calling process, and automatically reaped when you call s6lock_end(). It requires care with applications that trap SIGCHLD. It also requires care with lock file permissions: -a s6lockd instance might not be able +an s6lockd instance might not be able to open a lock file created by a former instance run by another client with different permissions.
  2. Use the s6lock_start() library call, together with a @@ -56,10 +56,10 @@ simplifies permissions management considerably.

    3. When run as a service, s6lockd has no "standalone" mode: it is designed to work with a Unix -domain superserver, like +domain super-server, like s6-ipcserver. -s6lockd follows the UCSPI -interface, it can be directly executed from the superserver. +s6lockd follows the UCSPI +interface, it can be directly executed from the super-server.

    Notes

    @@ -67,7 +67,7 @@ interface, it can be directly executed from the superserver. -- cgit v1.2.3