6cf21a6125
initial manpage. unfinished, I suck at manpages
179f891484
update manpage for new flags availables
3642040f5c
factorize #3:ban + simpler runcmd
b452300021
less verbose logs
fc07398e49
factorize #2: watch event + fix bug listening a bad file descriptor
icanserve
That's it, I think I have finished to turn iblock to a server. I'm curious how it handle stress of many attempts. Please test :)
e364ce9780
listen on localhost, both ipv4 and ipv6 if available. Use kqueue to handle many connections
306c003b1b
update rc : no reload
icanserve
My bad, that weren't zombies. Just duplicated listening sockets remaining. My bad. This should be ok now.
icanserve
I added a signal handler to catch child process. It seems to be called. However, "pgrep iblock" still find new process at each loop. Need someone better than me here to explain this behaviour.
icanserve
I'd like a review about zombie process if someone know how to check for such things, please.
5ac1e2631b
Don't need to copy strings around and hardcode the max table len from pf
550cfca6d1
Merge pull request 'fix_readme_path' (#4) from prx/iblock:fix_readme_path into main
f6e72657a5
Makefile: allow override of PREFIX
b95e736dc7
add fork check for error and reformat
a2702bad84
fix PREFIX in readme