Ubuntu
bandwidthd package

Branches for Wily

Name		Status	Last Modified	Last Commit
lp:ubuntu/wily/bandwidthd		1 Development	2015-07-06 07:48:07 UTC 2015-07-06	14. [ Paul Gevers ] * Improve use of dbco... Author: Andreas Henriksson Revision Date: 2015-07-06 07:48:07 UTC [ Paul Gevers ] * Improve use of dbconfig-common for bandwidthd-pgsql (Closes: #789445) - it never created a working configuration file - it didn't ask for cleanup - it didn't recommend postgresl server - the answers from dbconfig-common were used before the questions were asked, yielding old answers upon upgrade, and non-functional defaults when installing - Typo in prerm script prevented proper clean-up on removal * Add patch to change short <? notation to <?php * Add patch to replace deprecated $HTTP_GET_VARS by $_GET [ Andreas Henriksson ] * Demote newly added postgres recommends to suggests - The main purpose of bandwidthd-pgsql is to allow multiple "sensors" monitoring traffic at different nodes to report to a central (likely remote) database.
lp:ubuntu/wily-proposed/bandwidthd		1 Development	2015-07-06 07:48:07 UTC 2015-07-06	14. [ Paul Gevers ] * Improve use of dbco... Author: Andreas Henriksson Revision Date: 2015-07-06 07:48:07 UTC [ Paul Gevers ] * Improve use of dbconfig-common for bandwidthd-pgsql (Closes: #789445) - it never created a working configuration file - it didn't ask for cleanup - it didn't recommend postgresl server - the answers from dbconfig-common were used before the questions were asked, yielding old answers upon upgrade, and non-functional defaults when installing - Typo in prerm script prevented proper clean-up on removal * Add patch to change short <? notation to <?php * Add patch to replace deprecated $HTTP_GET_VARS by $_GET [ Andreas Henriksson ] * Demote newly added postgres recommends to suggests - The main purpose of bandwidthd-pgsql is to allow multiple "sensors" monitoring traffic at different nodes to report to a central (likely remote) database.