aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/src/signal.c (follow)
Commit message (Collapse)AuthorAge
* switch to egor@tensin.nameEgor Tensin2023-12-12
|
* sanitize #include-sEgor Tensin2023-07-04
|
* minor refactoringEgor Tensin2023-06-14
|
* signal: remove the stupid add_to_event_loop wrapperEgor Tensin2023-06-13
|
* signal: sigprocmask -> pthread_sigmaskEgor Tensin2023-06-13
|
* signal: refactoringEgor Tensin2023-06-13
|
* sanitize #include-sEgor Tensin2023-06-13
|
* signal: remove unused APIsEgor Tensin2023-06-13
|
* event_loop: hide the API detailsEgor Tensin2023-06-13
|
* use signalfd to stop on SIGTERMEgor Tensin2023-06-13
| | | | | | | | | | | | | | | | | | Is this an overkill? I don't know. The thing is, correctly intercepting SIGTERM (also SIGINT, etc.) is incredibly tricky. For example, before this commit, my I/O loops in server.c and worker.c were inherently racy. This was immediately obvious if you tried to run the tests. The tests (especially the Valgrind flavour) would run a worker, wait until it prints a "Waiting for a new command" line, and try to kill it using SIGTERM. The problem is, the global_stop_flag check could have already been executed by the worker, and it would hang forever in recv(). The solution seems to be to use signalfd and select()/poll(). I've never used either before, but it seems to work well enough - at least the very same tests pass and don't hang now.
* signal: refactoringEgor Tensin2023-05-15
|
* signal: refactoring, add comments in tcp_server, etc.Egor Tensin2023-05-15
|
* use -std=c17 -WpedanticEgor Tensin2023-05-13
|
* get rid of __attribute__((constructor))Egor Tensin2023-05-06
| | | | Explicit is better than implicit.
* add copyright noticesEgor Tensin2022-12-02
|
* log: refactoringEgor Tensin2022-09-08
|
* don't use the latest glibc featuresEgor Tensin2022-08-28
| | | | | pthread_attr_setsigmask_np is only available since 2.32, which is too modern.
* fix pthread error handlingEgor Tensin2022-08-26
| | | | pthread functions return positive error codes.
* worker: allow graceful shutdownsEgor Tensin2022-08-26
Well, maybe "graceful" is a strong word, but now you _can_ do ./server & ./worker & ./client ci_run URL REV && kill "$( pidof worker )" and the worker will wait for the CI run to complete.