[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Installed cricket 1.0.2-5 (all source)



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Format: 1.7
Date: Thu, 21 Dec 2000 23:28:37 -0500
Source: cricket
Binary: cricket
Architecture: source all
Version: 1.0.2-5
Distribution: unstable
Urgency: low
Maintainer: Matt Zimmerman <mdz@debian.org>
Changed-By: Matt Zimmerman <mdz@debian.org>
Description: 
 cricket    - Program for collection and display of time-series data
Closes: 80238
Changes: 
 cricket (1.0.2-5) unstable; urgency=low
 .
   * Added a daily cron job to clean out /var/cache/cricket.  This
     directory can contain a fixed maximum number of files (determined
     roughly by the number of targets in the config tree), but once a file
     is created, it is almost never removed. (Closes: #80238)
   * Fixed some questionable upstream defaults.  I'd wanted to change these
     for a long time, but was hesitant to diverge from upstream, lest
     I break configuration compatibility and violate the principle of least
     surprise.  I have since learned that these defaults will be changed in
     the next upstream release (1.0.3), so I went ahead and made the
     changes.  They are:
     - Use bytes=false for the ifInOctets and ifOutOctets targets.  This
       means that kb/sec, mb/sec, etc. will be computed as powers of 10 (1k
       = 10^3 = 1000) rather than powers of 2 (1k = 2^10 = 1024).  Much
       discussion on the cricket-users list has revealed that this is what
       people expect.
     - Use rrd-ds-type=DERIVE and rrd-min=0 for the default datasource.  This
       means that new targets will be created so that if the current sample
       of a counter is less than the previous sample, it will be discarded.
       Previously, it would be assumed that the counter had overflowed, and
       rrdtool would try to correct for that, assuming a 32-bit or 64-bit
       counter.  This would cause large, bogus spikes when an SNMP device was
       reset.  The vast majority of users would rather lose a sample in this
       case (and when a counter overflow occurs) than get a bogus one.
Files: 
 1de64c34c44f4c77d760cc09e3e2cbe6 568 net extra cricket_1.0.2-5.dsc
 85ee89ffeebbc9c75728c4e0a8cff50b 9676 net extra cricket_1.0.2-5.diff.gz
 d0e701d1b8f8d0fb4ed2dadd3eb868fb 316322 net extra cricket_1.0.2-5_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE6RFOVArxCt0PiXR4RAu3qAJ9V81cmo5Vu+Ctp6Kk2gHmnABuzDwCg0jmR
LP4Sgdhceen9FJDafIvECZ4=
=4NF3
-----END PGP SIGNATURE-----


Installed:
cricket_1.0.2-5.dsc
  to pool/main/c/cricket/cricket_1.0.2-5.dsc
cricket_1.0.2-5_all.deb
  to pool/main/c/cricket/cricket_1.0.2-5_all.deb
cricket_1.0.2-5.diff.gz
  to pool/main/c/cricket/cricket_1.0.2-5.diff.gz



Reply to: