/explore
|
You are here 
|
venam.net | ||
| | | | |
venam.nixers.net
|
|
| | | | | You've certainly heard of daemons, those processes that lurk in the background and do what they're supposed to do. You might even have written and run programs that are daemons. Today we'll talk about them, those daemons ({day,dee}mon), what there is to know about their mechanism and details. A big generic overview of daemons on ... | |
| | | | |
blog.koehntopp.info
|
|
| | | | | Kris Köhntopp's blog (Fedi: @isotoppinfosec.exchange) | |
| | | | |
thorstenball.com
|
|
| | | | | [AI summary] The article explains how Unicorn, a web server, leverages Unix system calls and concepts like fork, pipe, and signal handling to efficiently manage web requests. It highlights features such as hot reloading, zero downtime deployments, and worker process scaling using signals. The author emphasizes that these capabilities are not magic but a result of understanding and utilizing Unix's low-level mechanisms. The article also discusses the importance of knowing system-level details for debugging, architectural decisions, and deeper understanding of how software operates on the underlying system. | |
| | | | |
blog.nuculabs.dev
|
|
| | | I've recently finished reading a book called Practical Binary Analysis which I consider a state of the art book (review will come soon) and I would like to post my solution to the crackme found in chapter 5. | ||
