From: Jeff Garzik <jeff@garzik.org>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git daemon request logging?
Date: Fri, 15 May 2009 17:01:16 -0400 [thread overview]
Message-ID: <4A0DD81C.2000709@garzik.org> (raw)
In-Reply-To: <81b0412b0905151356t7bf613d5me39af08d37f72857@mail.gmail.com>
Alex Riesen wrote:
> 2009/5/15 Jeff Garzik <jeff@garzik.org>:
>> Does the git daemon do any sort of request logging? Could it?
>>
>> I was thinking it would be nice to see the amount of pulls/clones for each
>> git.kernel.org repository.
>
> Does this count?
>
> May 15 22:54:47 tigra git[28923]: connect from 192.168.0.8 (192.168.0.8)
> May 15 22:54:47 tigra git-daemon[28924]: Connection from 192.168.0.8:40845
> May 15 22:54:47 tigra git-daemon[28924]: Extended attributes (11
> bytes) exist <host=gate>
> May 15 22:54:47 tigra git-daemon[28924]: Request upload-pack for '~raa/src/git'
>
> fetch(pull)/clone are the same for daemon.
Honestly I was hoping for something more along the lines of httpd
one-line request logging, as the above is a lot of data to log + parse.
Jeff
next prev parent reply other threads:[~2009-05-15 21:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 19:39 git daemon request logging? Jeff Garzik
2009-05-15 20:56 ` Alex Riesen
2009-05-15 21:01 ` Jeff Garzik [this message]
2009-05-15 21:58 ` Junio C Hamano
2009-05-15 22:22 ` Robin H. Johnson
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4A0DD81C.2000709@garzik.org \
--to=jeff@garzik.org \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
/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.
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 NNTP newsgroup(s).