From 81c7a02ec870ef3dba9f8b8f8dbecbd119e5ea47 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Sat, 31 Dec 2016 10:55:56 +0000 Subject: Fifodir doc clarification (thanks Buck Evans) --- doc/fifodir.html | 38 +++++++++++++++++++++++++++++++++++++- 1 file changed, 37 insertions(+), 1 deletion(-) diff --git a/doc/fifodir.html b/doc/fifodir.html index 7dbddfa..eccdf5b 100644 --- a/doc/fifodir.html +++ b/doc/fifodir.html @@ -29,12 +29,14 @@ create fifodirs in a RAM filesystem.

C API

+

For the notifier

+ +

For a listener

+ + +

Unix API

+

For the notifier

+ + +

For a listener

+ +

Internals and Unix permissions

@@ -71,6 +98,15 @@ Karrmann.
  • To unsubscribe, a listener unlinks his named pipe from the directory.
  • +

    + Note that in the s6 implementation of fifodirs, there are a few additional +details: for instance, the named pipes created in a fifodir by a listener +follow a strict naming convention, for efficiency and safety reasons. If +you are using fifodirs, it is recommended that you use the provided C library +functions or the s6-ftrig-* command line utilities instead of +directly hacking into the fifodir internals. +

    +

    Fifodirs are created by, so they always originally have the same uid and gid as, their notifier. A notifier must be able to make his fifodir either publically -- cgit v1.3.1