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/s6lock.html | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'doc/libs6/s6lock.html') diff --git a/doc/libs6/s6lock.html b/doc/libs6/s6lock.html index 5eb580b..049ed44 100644 --- a/doc/libs6/s6lock.html +++ b/doc/libs6/s6lock.html @@ -40,7 +40,7 @@ options are usually available. s6lockd service concurrently accessed by several applications using such locks to gate shared resources. -
  • If you're not using a s6lockd service, +
  • If you're not using an s6lockd service, make sure your application is not disturbed by children it doesn't know it has. Using nonblocking waits, ignoring pids you don't know, and using a @@ -65,13 +65,13 @@ s6lock_start_g(&a, path, &deadline) ;

    -s6lock_start_g starts a session by connecting to a s6lockd service +s6lock_start_g starts a session by connecting to an s6lockd service listening on path. The working directory is set by the administrator of the service.
    -s6lock_startf_g starts a session with a s6lockd process as a child, +s6lock_startf_g starts a session with an s6lockd process as a child, using lockdir as its working directory.
    -a is a s6lock_t structure that must be declared in the stack and +a is an s6lock_t structure that must be declared in the stack and initialized to S6LOCK_ZERO. If the session initialization fails, the function returns 0 and errno is set; else the function returns 1. -- cgit v1.2.3