19:51 olgeni 

Remove all space characters from Makefile assignments.

No functional changes included.

CR:		D193 (except math/sedumi)
Approved by:	portmgr (bapt)

 

18:54 antoine 

Reset a few maintainers who are unreachable

With hat:	portmgr

 

22:24 bapt 

Add NO_STAGE all over the place in preparation for the staging support (cat:
net-mgmt)

 

06:28 jgh 

- Add New USES macro to handle support for Zenoss ports and Zenpacks:
    USES= zenoss
-trim historical headers

Convert net-mgmt/zenpack family to new framework

PR:		176723
Approved by:	maintainer timeout ( 14 days )

 

21:59 jgh 

- remove pkg-plist in favor of PLIST_FILES and PLIST_DIRS

01:21 jgh 

- Fix fetch error by updating MASTER_SITES and DISTFILE

PR:     ports/164107
Submitted by: Anthony Garcia <agarcia at experts-exchange.com>
Approved by:    crees,rene (mentors, implicit)

14:36 crees 

When troubleshooting network issues, it can be very useful to have all the
interface graphs for a device on the same screen. This helps with spotting
trends, or tracing where traffic is flowing through a switch or router. The
only way to natively achieve this with Zenoss is to create a graph or
multi-graph report for every network device manually, which can be a chore
if you have more than a few network devices.

This ZenPack provides a new link on the left side of a device detail view
called "Interface Graphs" - this view shows the graphs for all of the network
interfaces on the device in one place, allowing for fast spotting of issues
or traffic flows. Both the interface name and the description (if any) are
used to title the graphs to aid with identification.

Note that with stacked switches, you can end up with a very large number of
graphs on the page, so tuning this slightly via the configuration properties
below could be a good idea in these situations.

WWW: http://community.zenoss.org/docs/DOC-10226

PR:             ports/157503
Submitted by:   Zenoss <zenoss@experts-exchange.com>