Logging api

Reviewers:  @bernerdschaefer, @peterbourgon 

First pass at the internals of the logging API.  This is two layers thick.  There is a RingBuffer for log messages, and on top of this is a data structure that implements storage for and operations for each container.  (The RingBuffer probably should have been a separate submit.)

The next piece to be worked on will be the HTTP logging interface.
Thanks for catching that.


On Wed, Jul 30, 2014 at 5:42 PM, Bernerd Schaefer <notifications@github.com>
wrote:

> In harpoon-agent/main.go:
>
> > @@ -29,9 +29,7 @@ func init() {
> >  }
> >
> >  func main() {
> > -	go receiveLogs()
> > -
> > -	flag.Int64Var(&agentTotalCPU, "cpu", -1, "available cpu resources (-1 to use all cpus)")
> > +	flag.Int64Var(&agentTotalCPU, "cpu", -1, "available cpu resourcesx (-1 to use all cpus)")
>
> s/resourcesx/resources
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/soundcloud/harpoon/pull/13/files#r15592032>.
>