From 6f85f86357d70570195e7a97a8b7fbb779c82230 Mon Sep 17 00:00:00 2001 From: Laurent Bercot Date: Tue, 23 May 2017 11:03:22 +0000 Subject: Switch doc to schemeless URLs --- doc/libs6/ftrigr.html | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) (limited to 'doc/libs6/ftrigr.html') diff --git a/doc/libs6/ftrigr.html b/doc/libs6/ftrigr.html index 889e389..3a32c7e 100644 --- a/doc/libs6/ftrigr.html +++ b/doc/libs6/ftrigr.html @@ -6,15 +6,15 @@ s6: the ftrigr library interface - +

libs6
s6
-Software
-skarnet.org +Software
+skarnet.org

The ftrigr library interface

@@ -37,7 +37,7 @@ exact function prototypes. know it has. This means paying some attention to the SIGCHLD handler, if any, and to the way you perform waitpid()s. The best practice is to use a -self-pipe +self-pipe to handle SIGCHLD (as well as other signals the application needs to trap), and to always use wait_nohang() to reap children, simply ignoring pids you don't know. @@ -67,7 +67,7 @@ parameter. Those are pointers to tain_t structures containing absolute times; the former represents a deadline (in most cases, this time will be in the future) and the latter must be an accurate enough timestamp. These structures can be filled using the tain_ primitives declared in -skalibs/tai.h. +skalibs/tai.h.
  • ("Accurate enough" means that no blocking system call must have been made since the last time stamp was updated (by tain_now(&stamp)). It's a good policy to always update @@ -88,7 +88,7 @@ of the current time. This allows the programmer to call several such functions in a sequence without modifying the deadline and stamp parameters: then the whole sequence is bound in execution time.
  • This is a general safety mechanism implemented in -libunixonacid: +libunixonacid: in interprocess communication, purely synchronous primitives are dangerous because they make the calling process rely on proper behaviour of the called process. Giving synchronous primitives the ability to timeout allows developers -- cgit v1.3.1