moonbridge
diff reference.txt @ 280:1a4f89f4c712
Modified behavior of moonbridge_io.signalsocket(...); Fixed usage of moonbridge_io.signalsocket(...) in moonbridge_http module
author | jbe |
---|---|
date | Tue Jun 06 21:58:26 2017 +0200 (2017-06-06) |
parents | d4c82c90d244 |
children | 6bb191b6ead5 |
line diff
1.1 --- a/reference.txt Tue Jun 06 20:19:09 2017 +0200 1.2 +++ b/reference.txt Tue Jun 06 21:58:26 2017 +0200 1.3 @@ -399,15 +399,14 @@ 1.4 ### moonbridge_io.signalsocket(signal) 1.5 1.6 This function installs a signal handler. As argument, either the signal number 1.7 -is passed (e.g. 15) or a name (e.g. "TERM"). 1.8 - 1.9 -The function returns a new socket object that receives a character (".") each 1.10 -time a signal is received. 1.11 +is passed (e.g. 15) or a name (e.g. "TERM"). The function returns a socket 1.12 +object that receives a character (".") each time a signal is received. 1.13 1.14 -Note that each socket object has an independent buffer. It is thus recommended 1.15 -to always read all bytes, e.g. by using the expression: 1.16 +The function can be called multiple times, in which case the same socket object 1.17 +is returned. The returned socket should never be closed by the caller. 1.18 1.19 -#(assert(sigsock:read_nb())) > 0 -- true if signal occurred 1.20 +The process should not be forked after calling this function (except for 1.21 +replacing the process with another program). 1.22 1.23 1.24 ### moonbridge_io.tcpconnect(hostname, port)