>> This is possible for only a restricted set of services (those that
>> are at least conceptually datagram services, more or less).
> I don't think it precludes tcp as long as they are stateless - http
> is an obvious example
Ish. HTTP is stateless in the sense that consecutive
On Thu, Mar 17, 2022 at 04:58:56PM +1030, Brett Lymn wrote:
> Perhaps a shim program that manages a socket between it and the
> underlying daemon - the shim can talk to inetd to coordinate the handoff
> of an incoming connection and also being put back onto the idle pool
> when the connection
On Wed, Mar 16, 2022 at 07:42:26AM +0100, Martin Husemann wrote:
>
> How does inetd replace their stdin once the connection is established?
Perhaps a shim program that manages a socket between it and the
underlying daemon - the shim can talk to inetd to coordinate the handoff
of an incoming
On Tue, Mar 15, 2022 at 05:45:48PM -0400, Mouse wrote:
>
> This is possible for only a restricted set of services (those that are
> at least conceptually datagram services, more or less). For example, I
> have a machine with an inetd entry which uses a script running nc to
> forward connections
On Wed, Mar 16, 2022 at 07:53:09AM +1030, Brett Lymn wrote:
> They wait on stdin, they don't need to signal done.
How does inetd replace their stdin once the connection is established?
Many deamons will do socket operations (e.g. querying the peer) early
on startup - that would fail (or deliver
>>> [inetd reusing preforked processes after use]
>> This doesn't even make sense unless (a) you keep a separate list for
>> each service, (b) the daemon is expecting this (and thus signals its
>> doneness by some means other than exiting), (c) you invent some
>> interface for passing each new
On Tue, Mar 15, 2022 at 08:36:09AM -0400, Mouse wrote:
>
> This doesn't even make sense unless (a) you keep a separate list for
> each service, (b) the daemon is expecting this (and thus signals its
> doneness by some means other than exiting), (c) you invent some
> interface for passing each new
>>> Here's what Christos had to say about it: "Means that once a
>>> preforked child is done you can either wait(2) for it and end it or
>>> you can put it back of the list of available processes so that it
>>> can handle more requests."
This sounds nonsensical to me.
>> Yeah, it does seem
On Mon, Mar 14, 2022 at 04:24:23PM -0700, Arjun wrote:
>
> > My senior project group didn't get around to implementing
> > "pre-forking", so that should be interesting to implement! Here's what
> > Christos had
> > to say about it: "Means that once a preforked child is done you can
> > either
> 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
I guess looking at the test output again, it looks like inetd isn't
reading the config file (inetd_ratelimit.conf) properly. Notice the
lines that say "FREE", meaning it deleted those services. I think
what's going on is you have the current version of inetd installed on
your machine, which is
> I wrote t_inetd.c as part of my senior project for college six months
> ago (as part of implementing some of the "inetd enhancements"
> project).
> It's most likely my fault it isn't working. t_inetd.c is quite fragile
> since it just uses a range of ports on the host machine.
> You could try
Hello Arjun,
I wrote t_inetd.c as part of my senior project for college six months
ago (as part of implementing some of the "inetd enhancements"
project).
It's most likely my fault it isn't working. t_inetd.c is quite fragile
since it just uses a range of ports on the host machine.
You could try
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 children
14 matches
Mail list logo
