Age | Commit message (Collapse) | Author | Files | Lines |
|
pkglint -Wall -F --only aligned --only indent -r
Manually excluded consolekit and dc-tools since pkglint didn't get the
formatting correct.
|
|
future Python 3.8
|
|
python 3.4 / 3.5 removal commit.
|
|
- Includes some whitespace changes, to be handled in a separate commit.
|
|
This is a semi-manual PKGREVISION bump.
|
|
|
|
|
|
|
|
|
|
Problems found with existing digests:
Package memconf distfile memconf-2.16/memconf.gz
b6f4b736cac388dddc5070670351cf7262aba048 [recorded]
95748686a5ad8144232f4d4abc9bf052721a196f [calculated]
Problems found locating distfiles:
Package dc-tools: missing distfile dc-tools/abs0-dc-burn-netbsd-1.5-0-gae55ec9
Package ipw-firmware: missing distfile ipw2100-fw-1.2.tgz
Package iwi-firmware: missing distfile ipw2200-fw-2.3.tgz
Package nvnet: missing distfile nvnet-netbsd-src-20050620.tgz
Package syslog-ng: missing distfile syslog-ng-3.7.2.tar.gz
Otherwise, existing SHA1 digests verified and found to be the same on
the machine holding the existing distfiles (morden). All existing
SHA1 digests retained for now as an audit trail.
|
|
until proven otherwise.
|
|
either because they themselves are not ready or because a
dependency isn't. This is annotated by
PYTHON_VERSIONS_INCOMPATIBLE= 33 # not yet ported as of x.y.z
or
PYTHON_VERSIONS_INCOMPATIBLE= 33 # py-foo, py-bar
respectively, please use the same style for other packages,
and check during updates.
Use versioned_dependencies.mk where applicable.
Use REPLACE_PYTHON instead of handcoded alternatives, where applicable.
Reorder Makefile sections into standard order, where applicable.
Remove PYTHON_VERSIONS_INCLUDE_3X lines since that will be default
with the next commit.
Whitespace cleanups and other nits corrected, where necessary.
|
|
Collection.
Monitoring is an API with a DSL feel to write monitoring daemons in Python.
Monitoring works well for the following tasks:
* to be notified when incidents happen (email, XMPP, ZeroMQ...)
* automatic actions to be taken (restart, rm, git pull...)
* to collect system statistics for further processing e.g. graphs
* tie into existing/third-party Python code
* play along nicely with existing deployment/configuration ecosystem
(fabric/cuisine)
Overview
* monitoring DSL: declarative programming to define monitoring strategy
* wide spectrum: from data collection and incident reporting to taking
automatic actions
* Small, easy to read, a single file API
* Revised BSD License
Use Cases
* ensure service availability: test and start/stop when problems
* collect system statistics/data, log locally and/or remotely
* alert on system/service health, take actions
|