Your message dated Wed, 21 Sep 2005 16:00:49 -0600
with message-id <[EMAIL PROTECTED]>
and subject line WNPP bug closing
has caused the attached Bug report to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what I am
talking about this indicates a serious mail system misconfiguration
somewhere.  Please contact me immediately.)

Debian bug tracking system administrator
(administrator, Debian Bugs database)

--------------------------------------
Received: (at submit) by bugs.debian.org; 11 Mar 2004 16:54:08 +0000
>From [EMAIL PROTECTED] Thu Mar 11 08:54:08 2004
Return-path: <[EMAIL PROTECTED]>
Received: from frogcircus.org [66.45.230.197] 
        by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
        id 1B1TRf-0005cl-00; Thu, 11 Mar 2004 08:54:08 -0800
Received: from localhost (localhost [127.0.0.1])
  (uid 1000)
  by frogcircus.org with local; Thu, 11 Mar 2004 11:54:05 -0500
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Charles Fry <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: RFP: netlogger -- distributed system logging tool
X-Mailer: reportbug 2.48
Date: Thu, 11 Mar 2004 11:54:05 -0500
Message-ID: <[EMAIL PROTECTED]>
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_08 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-5.0 required=4.0 tests=HAS_PACKAGE autolearn=no 
        version=2.60-bugs.debian.org_2004_03_08
X-Spam-Level: 

Package: wnpp
Severity: wishlist

* Package name    : netlogger
  Version         : 2.2.5
  Upstream Author : Dan Gunter <[EMAIL PROTECTED]>
* URL             : http://www-didc.lbl.gov/NetLogger/
* License         : GPL
  Description     : distributed system logging tool

Instrument distributed applications to log events for analysis based on
time correlated and/or object correlated events. Includes the following
components:

 * NetLogger message format and data model: A simple, common message
   format for all monitoring events which includes high-precision
   timestamps

 * NetLogger client API library:  C/C++, Java, and Python calls that you
   add to your existing source code to generate monitoring events. The
   destination and logging level of NetLogger messages are all easily
   controlled using an environment variable.

 * NetLogger visualization tool (nlv) : a powerful, customizable
   X-Windows tool or viewing and analysis of event logs based on time
   correlated and/or object correlated events.

 * NetLogger host/network monitoring tools: a collection of instrumented
   system monitoring tools: nl_vmstat, nl_netstat, nl_tcpdump, an
   interface to  Ganglia, etc.

 * NetLogger storage and retrieval tools, including:
    * netlogd: a daemon that collects NetLogger events from several
      places at a single, central host
    * Archive: An event archive system for NetLogger data, based on
      mySQL
    * nlforward: forward all netlogger files in a specified directory to
      a given location

Perhaps several related packages could be created for the different
components.

Charles

-- System Information:
Debian Release: testing/unstable
  APT prefers testing
  APT policy: (800, 'testing'), (90, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.4.25-5um
Locale: LANG=en_US, LC_CTYPE=en_US


---------------------------------------
Received: (at 237456-done) by bugs.debian.org; 21 Sep 2005 22:00:49 +0000
>From [EMAIL PROTECTED] Wed Sep 21 15:00:49 2005
Return-path: <[EMAIL PROTECTED]>
Received: from merkel.debian.org [192.25.206.16] (mail)
        by spohr.debian.org with esmtp (Exim 3.36 1 (Debian))
        id 1EICe1-0005A6-00; Wed, 21 Sep 2005 15:00:49 -0700
Received: from damog by merkel.debian.org with local (Exim 3.36 1 (Debian))
        id 1EICe1-0004Rg-00; Wed, 21 Sep 2005 16:00:49 -0600
To: [EMAIL PROTECTED]
Subject: WNPP bug closing
Message-Id: <[EMAIL PROTECTED]>
From: David Moreno Garza <[EMAIL PROTECTED]>
Date: Wed, 21 Sep 2005 16:00:49 -0600
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 
        (1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Level: 
X-Spam-Status: No, hits=-5.0 required=4.0 tests=BAYES_00,VALID_BTS_CONTROL 
        autolearn=no version=2.60-bugs.debian.org_2005_01_02

Hello,

This is an automatic mail sent to close the RFP you have reported or 
are involved with.

Your RFP wnpp bug is being closed because of the following reasons:
- It is, as of today, older than 450 days.
- It hasn't had any activity recently.

As this an automatic procedure, it could of course have something
wrong and probably it would be closing some bugs that are not 
intended by owners and submitters (like you) to be closed, for
example if the RFP is still of your interest, or there has been 
some kind of activity around it. In that case, please reopen the
bug, do it, DO IT NOW! (I don't want to be blamed because of
mass closing and not let people know that they can easily reopen
their bugs ;-).

To re-open it, you simply have to mail [EMAIL PROTECTED]
with a body text like this:

reopen 237456
thanks bts

Further comments on the work done in the bug sent to
[EMAIL PROTECTED] would be truly welcomed.
Anyway, if you have any kind of problems when dealing with
the BTS, feel free to contact me and I'd be more than happy to help
you on this: <[EMAIL PROTECTED]>.

This is the second massive wnpp closing that is being done. The next close
will be done on inactive RFPs older than 365 days and finally, an automatic
script will close, by default, *inactive* RFPs when they reach one year of
inactivity.

A similar process is being applied to other kind of wnpp bugs.

Thanks for your cooperation,

 -- David Moreno Garza <[EMAIL PROTECTED]>  Wed, 20 Sep 2005 17:06:42 -0500


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to