git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: "Robin H. Johnson" <robbat2@gentoo.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git daemon inetd mode: need traffic statistics
Date: Tue, 27 Sep 2022 00:26:36 +0000	[thread overview]
Message-ID: <YzJDPNvi5rpN54E6@tapette.crustytoothpaste.net> (raw)
In-Reply-To: <robbat2-20220926T041714-401286569Z@orbis-terrarum.net>

[-- Attachment #1: Type: text/plain, Size: 982 bytes --]

On 2022-09-26 at 04:21:46, Robin H. Johnson wrote:
> Has anybody got patchsets that let git-daemon send traffic data (to
> syslog) at the end of each request, about the peer, and how many bytes
> in each direction?
> 
> Hoping somebody has something useful to share that isn't coming up in my
> research.

I don't, sorry.  At work we use a custom proxy which provides this,
which I can't share and probably wouldn't be of much use to you even if
I could since it's very specific to our setup.

My impression is that typically most hosters are moving away from port
9418 because it isn't encrypted or secured and anonymous HTTPS is just
as easy to use.  As a consequence, git-daemon isn't typically seeing a
lot of development since it is seeing less and less use.  Having said
that, I'm sure a patch to git-daemon implementing this feature would be
welcome, whether from you or from someone else.
-- 
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 263 bytes --]

      reply	other threads:[~2022-09-27  0:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-26  4:21 git daemon inetd mode: need traffic statistics Robin H. Johnson
2022-09-27  0:26 ` brian m. carlson [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: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=YzJDPNvi5rpN54E6@tapette.crustytoothpaste.net \
    --to=sandals@crustytoothpaste.net \
    --cc=git@vger.kernel.org \
    --cc=robbat2@gentoo.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://80x24.org/mirrors/git.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).