2007/399 inetd backlog SMF property: connection_backlog

[Brian Utterback]

Any chance that this property can be made per service? I've always
thought that this should really be configurable on a per service
basis. When you think about it, all those customers asking for this
feature really hit this limit on one or two services and need to
increase those. Why must we increase them all? The 10 connection
default is just fine for most services.

Liane Praza wrote:
> I'm submitting this open FastTrack on behalf of Vineeth Pillai.  It
> re-introduces the inetd connection backlog tunable as an inetd property,
> at a stability of Committed, with a Patch release binding.
> 
> Timeout expires on 7/11/2007.
> 
> ---
> 
> 1. Project Description:
>    We plan to introduce an interface to inetd, to change the default
>    connection backlog queue size. This interface would be an SMF
>    property which can be changed via SMF commands.
> 
>    Till Solaris 9, there was an interface to inetd through which we
>    could specify the size of the backlog queue maintained by inetd. The
>    option was -l <queue length> as specified in "Inetd Backlog Flag"
>    (PSARC/1995/319) as public.
> 
>    In Solaris 10, this option was erroneously removed and has been
>    requested by customers.  We intend to re-introduce the option
>    as a committed inetd SMF property: connection_backlog.  This will
>    continue to control the number of incoming connection requests that
>    are temporarily queued at the server end point and later transformed
>    into connections(if accepted by the server applications) on a seperate
>    end point.
> 
>    The default value is unchanged by this proposal and continues to be
>    10. Admins can customize the value through the standard inetadm(1M)
>    interface.
> 
> 2. Interface table
> 
>     Property            Stability
>     --------            ---------
>     connection_backlog  Committed 
> 
> 3. Doc Impact:
>    Manpage of inetd and inetadm would be modified to add this new
>    interface change:
> 
>    inetd(1M) manpage diffs
>    ---------------------------------------------------------------------
>    --- inetd.man   Wed Jul  4 12:07:29 2007
>    +++ inetd.man_new       Wed Jul  4 12:09:44 2007
>    @@ -496,9 +496,13 @@
>                           values 0 and -1 specify that copies lim-
>                           iting is disabled.
> 
>    +    connection_backlog      The backlog queue size. It represents a
>    +                            bound on the number of incoming client
>    +                            requests that are queued at the listening
>    +                            endpoints for servers.
> 
>    +
>       name                Can be  set  to  one  of  the  following
>                           values:
> 
>    @@ -706,6 +710,7 @@
>            bind_fail_interval  -1
>            bind_fail_max       -1
>            con_rate_offline    -1
>    +       connection_backlog  10
>            failrate_count      40
>            failrate_time       60
>            inherit_env         true
> 
>    ---------------------------------------------------------------------
> 
>    inetadm(1M) manpage diffs
>    ----------------------------------------------------------------------
> 
>    --- inetadm.man Wed Jul  4 11:58:20 2007
>    +++ inetadm.newman      Wed Jul  4 11:58:06 2007
>    @@ -234,6 +234,7 @@
>            default  inherit_env=TRUE
>            default  tcp_trace=FALSE
>            default  tcp_wrappers=FALSE
>    +       default  connection_backlog=10
> 
>          Example 2 Displaying Default Properties
> 
>    @@ -255,6 +256,7 @@
>            inherit_env=TRUE
>            tcp_trace=FALSE
>            tcp_wrappers=FALSE
>    +       connection_backlog=10
> 
>    @@ -301,6 +303,7 @@
>            default  inherit_env=TRUE
>                    tcp_trace=TRUE
>            default  tcp_wrappers=FALSE
>    +       default  connection_backlog=10
> 
>    ---------------------------------------------------------------------
> 
> 4. References:
>    PSARC case: PSARC/1995/319
> 

-- 
blu

The #1 red flag for privacy advocates is when a law enforcement
official says "If you aren't doing anything wrong, then you have
nothing to worry about."
----------------------------------------------------------------------
Brian Utterback - Solaris RPE, Sun Microsystems, Inc.
Ph:877-259-7345, Em:brian.utterback-at-ess-you-enn-dot-kom