Thank you for your concerns,
> Wouldn't this better be a separate daemon?
I chose inetd because it is already built to spawn and monitor processes.
Creating a separate daemon would involve replicating a lot of this code into
another codebase.
Additionally, the new parameters that I am adding sh
-Summer-of-Code-inetd-22/blob/main/inetdproposal.pdf
(this was my proposal)
Arjun
> I think what's going on is you have the current version of inetd installed on
> your machine, which is what the test cases run
What do you mean by “current”?
> You'll have to go to the usr.sbin/inetd source directory and do "make
> install”,
> which will replace the program that's installed
or you can put it back of the list
> of available processes so that it can handle more requests." It's kind
> of a confusing concept to me!
Yeah, it does seem confusing to actually implement.
- Arjun
Hello NetBSD community,
I am arjun and would like to participate in Google’s Summer of Code
2022. I’ve always wanted to participate in open source work and am excited to
start here :^)
The inetd enhancements project caught my eye, particularly the
"pre-forking multiple chi
