Re: Very basic traffic measurement for svnserve?

Brian W. Fitzpatrick wrote:
> Ah! Now I understand... sorry for my rude comment earlier. I don't
> really have a problem with writing to stdout when running in the
> foreground, but who runs their daemons in the foreground? I assume that
> the daemontools do?

It's only a daemon because you run it that way. For me, it is simply a long
running server process. I won't argue the advantages to each mode with you.
Just know that, to my mind, if svnserve is run in the foreground (for whatever
reason), the only sane thing to do with log entries is to send them to stdout.
It makes for efficient debugging, for no other reason.

> Well, I would advocate spending a bit of list time figuring out what
> needs to get logged where before we try to figure out how it gets
> logged.

Chicken, I'd like you to meet egg! ;-) The discussion of how to structure a log
framework leads inevitably to a good discussion of what gets logged and where.
For example:

  - does logging happen at every level of the code (public vs. private) or does
logging only happen at well defined layers

  - do we just add a logging callback to many/all of the composite data objects
in the system, or just make it a single helper routine available from any module

  - do we define /a priori/ log levels (ala syslog) or do we let those evolve as
the structure becomes defined (then map those internal levels to external
levels, in the case of a syslog interface)

I had some of this discussion with Brane a couple of months ago; I'll see if I
can find it in the archive.

John

-- 
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org