From: Eric Wong <normalperson@yhbt.net>
To: raindrops@librelist.org
Subject: Re: Socket & Symlinks
Date: Mon, 4 Jun 2012 18:12:50 +0000 [thread overview]
Message-ID: <20120604181250.GA8696@dcvr.yhbt.net> (raw)
In-Reply-To: CALO9HP21RusiP0C8gYH-GHCLanoC56JGGn9nz_5vmNLhXud7tA@mail.gmail.com
Brian Corrigan <bcorrigan78@gmail.com> wrote:
> Hi Folks -
>
> After trying to figure out why I always get 0 for both active and
> queued stats, I noticed the unix_listener_stats method doesn't resolve
> symlinks (which are common due to the way a lot of deployment recipes
> deploy rails apps) prior to looking up the socket in the proc file.
>
> I was considering a small patch that would require the standard
> pathname library and resolve each path prior to encoding them. Would
> this be accepted?
I'd have to see the patch, but the idea sounds good.
prev parent reply other threads:[~2012-06-04 18:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-04 15:49 Socket & Symlinks Brian Corrigan
2012-06-04 18:12 ` Eric Wong [this message]
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=20120604181250.GA8696@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--cc=raindrops@librelist.org \
/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).