raindrops RubyGem user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Eric Wong <bofh@yhbt.net>
To: Jean Boussier <jean.boussier@gmail.com>
Cc: raindrops-public@yhbt.net
Subject: [squash] make reusing inet_diag sock fork+preload safe
Date: Sat, 30 Sep 2023 23:35:06 +0000	[thread overview]
Message-ID: <20230930233506.M141715@dcvr> (raw)
In-Reply-To: <20230930231320.M781709@dcvr>

I'll squash this in for fork+preload safety.
Fwiw, most of the stats stuff has never seen any real-world use
to my knowledge :x   Somebody else got me to work on it but never
got around to using it, so you're probably the only guinea pig :>

diff --git a/lib/raindrops/middleware.rb b/lib/raindrops/middleware.rb
index e0781f2..a9e2ee3 100644
--- a/lib/raindrops/middleware.rb
+++ b/lib/raindrops/middleware.rb
@@ -98,8 +98,6 @@ def initialize(app, opts = {})
       tmp = Unicorn.listener_names
     end
     @nl_sock = @tcp = @unix = nil
-    defined?(Raindrops::Linux.tcp_listener_stats) and
-      @nl_sock = Raindrops::InetDiagSocket.new
 
     if tmp
       @tcp = tmp.grep(/\A.+:\d+\z/)
@@ -131,6 +129,7 @@ def stats_response  # :nodoc:
            "writing: #{@stats.writing}\n"
 
     if defined?(Raindrops::Linux.tcp_listener_stats)
+      @nl_sock ||= Raindrops::InetDiagSocket.new
       Raindrops::Linux.tcp_listener_stats(@tcp, @nl_sock).each do |addr,stats|
         body << "#{addr} active: #{stats.active}\n" \
                 "#{addr} queued: #{stats.queued}\n"

  reply	other threads:[~2023-09-30 23:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23  9:56 [PATCH] tcp_listener_stats: always eagerly close sockets Jean Boussier
2023-09-26 21:40 ` Eric Wong
2023-09-30 23:13   ` [PATCH] middleware: reuse inet_diag netlink socket Eric Wong
2023-09-30 23:35     ` Eric Wong [this message]
2023-12-29 17:44       ` [PATCH v3] " Eric Wong

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://yhbt.net/raindrops/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230930233506.M141715@dcvr \
    --to=bofh@yhbt.net \
    --cc=jean.boussier@gmail.com \
    --cc=raindrops-public@yhbt.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/raindrops.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).