diff options
| author | Gabriel Schneider <[email protected]> | 2026-11-17 00:59:14 -0300 |
|---|---|---|
| committer | Gabriel Schneider <[email protected]> | 2026-11-17 10:06:26 -0300 |
| commit | 7f418a6bb3c2d5319d781a61a14aeaf15aff4c89 (patch) | |
| tree | 6b3324331fe2e4ed195e4864eca8362d4137b9bf /9proc | |
| parent | b44d970c121a65e1f9de04fee600a3b495fb6c96 (diff) | |
| download | cloud9-7f418a6bb3c2d5319d781a61a14aeaf15aff4c89.tar.gz cloud9-7f418a6bb3c2d5319d781a61a14aeaf15aff4c89.zip | |
Fsys: a deadline on every call, so a silent server is a timeout
A server that accepted and then said nothing held the caller for ever:
Fsys read its socket with no limit, the version in init included, while
pardes's own client gives a call 2 s and a write that runs a command
30 s. Fsys gains one field, `timeout` (an Io.Timeout), which init sets
to `default_timeout`, 30 s, before it speaks; each call's answer is read
by operateTimeout until that long after the call is sent, and past it the
call is error.Timeout (the answer may come yet, under a tag the next call
does not expect, so the connection is to be closed). `.none` waits for
ever: verbs' follow sets it, since following an event file waits as long
as the events take; read, ls, ask and the rest keep the deadline and say
"no answer in 30000 ms; fs follow waits for ever".
Test: a held read nobody feeds, on a 100 ms timeout, is error.Timeout
after 90-5000 ms (poll counts whole milliseconds). cloud9's test 108 of
108; serve's "two clients at once" and "repeated connect/disconnect"
failed once each at load 13 and passed in the four runs after, as on the
base: they do not touch Fsys.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Claude-Session: https://claude.ai/code/session_016Y9MNBECMWcJD5pdS4SR6T
Diffstat (limited to '9proc')
0 files changed, 0 insertions, 0 deletions
