All of lore.kernel.org
 help / color / mirror / Atom feed
From: Fabio M. Di Nitto <fabbione@ubuntu.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] Re: clulog
Date: Tue, 08 May 2007 08:52:37 +0200	[thread overview]
Message-ID: <46401E35.6070108@ubuntu.com> (raw)
In-Reply-To: <20070507181012.GE29015@redhat.com>

Lon Hohberger wrote:

> 
> Really - what we need is a better logging system.  clulog is just a
> wrapper around syslog.

Yes exactly as some other log.c/.h that are around the tree.

>  Some of the features we really need are:
> 
>  * ring-buffer style (w/ a fixed max size)
>    * Remove oldest / lowest-prio log messages if we run out of
>      room
>  * option of guaranteed non-blocking logging
> 
> clulog could be expanded and library-ified - esp. now that we have a
> better / single build system.
> 
> What I'd do is:
> 
>   * clulog_init(const char *facility, int mode, int severity)
> 	  MODE_SIMPLE   - what we have now.
>       MODE_NONBLOCK - simple nonblocking syslog() calls.  e.g. do what
> 		syslog() does, but open the log device O_NONBLOCK; lossy.
>       MODE_RINGBUF  - Non-blocking; fixed maximum memory footprint.
>         Clears lowest-prio / oldest log messages first if we fill up.
> 
> etc... etc...  I'll do more on this later. 

How would you feel if we first extract the code in its own library,
switch all the subproject to it and then implement features?

I think that in this way we will have to look at much less code than we
have now.

Thanks
Fabio

-- 
I'm going to make him an offer he can't refuse.



  reply	other threads:[~2007-05-08  6:52 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-07 18:10 [Cluster-devel] clulog Lon Hohberger
2007-05-08  6:52 ` Fabio M. Di Nitto [this message]
2007-05-15 18:13   ` [Cluster-devel] clulog Steven Dake
2007-05-15 18:24     ` Fabio Massimo Di Nitto
2007-05-15 21:06       ` Lon Hohberger

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=46401E35.6070108@ubuntu.com \
    --to=fabbione@ubuntu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.