| Commit message (Collapse) | Author | Age |
|---|
| ... | |
| |
|
|
|
|
| |
do { ... } while (0) is objectively better:
https://stackoverflow.com/q/1067226/514684
|
| |
|
|
| |
pthread functions return positive error codes.
|
| |
|
|
|
|
|
|
|
|
| |
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.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a basic "worker" program.
You can now do something like
./server &
./worker &
./client ci_run URL REV
and the server should pass a message to worker, after which it should
clone the repository at URL, checkout REV, and try to run the CI script.
It's extremely unfinished: I need to sort out the graceful shutdown, how
the server manages workers, etc.
|
| |
|
|
| |
This is a dumb warning.
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
| |
First, rename all API functions so that they start with net_.
Second, abstract the basic TCP server functionality into tcp_server.c.
This includes reworking net_accept so that it's a simple blocking
operation, and putting the callback stuff to tcp_server.c. Also, the
server now uses detached threads instead of fork(), since I want
connection handlers to share memory.
|
| | |
|
| | |
|
| |
|
|
| |
This I feel better conveys the meaning.
|
| | |
|
| | |
|
| |
|
|
| |
I've only recently learned about this flag, seems generally useful.
|
| |
|
|
| |
Make sure we handle read() returning 0, this is a valid use-case.
|
|
|
A basic client-server app, the client sends commands as an array of
strings. Hopefully I didn't mess up, and hopefully it'll be useful.
|
