Liane Praza wrote: > I'm filing this case for Gary as closed-approved-automatic, as it seems > an obvious extension to existing interface. As usual, speak up if you'd > like to see it promoted to a fasttrack. > > liane > > --- > > tcp_keepalive For inetd Services > Gary Mills > 08/27/2009 > > 1. Summary > > The inetd restarter defines a set of properties to control the behaviour > of the services it manages. This case adds the option `tcp_keepalive' > to the inetd restarter. Setting this option enables the TCP keepalive > facility for connections to services managed by inetd. It's needed > because some services do not have the ability to enable this facility by > themselves.
This is quite different from any of the existing inetd configuration parameters - inetd doesn't currently allow manipulation of socket configuration parameters. Please can you describe a case where this is intended to be used? (I ask, because mostly whenever I do see it being used, the author misunderstood what it does and shouldn't have been using it.) Why do you intend to allow access to this socket parameter, but no others (such as SO_SNDBUF, SO_RCVBUF, etc)? -- Cheers Andrew
