Summary: | vnstat: Statistics are not being updated on some systems any more | ||
---|---|---|---|
Product: | IPFire | Reporter: | Michael Tremer <michael.tremer> |
Component: | --- | Assignee: | Matthias Fischer <matthias.fischer> |
Status: | CLOSED FIXED | QA Contact: | |
Severity: | Major Usability | ||
Priority: | Will affect most users | CC: | matthias.fischer, peter.mueller |
Version: | 2 | Keywords: | 5MinuteJob |
Hardware: | unspecified | ||
OS: | Unspecified |
Description
Michael Tremer
2020-02-27 11:15:39 UTC
Being curious, I did a quick research. Creating this file was triggered here (2019-05-21): https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;f=lfs/vnstat;h=b0d31edbd6268e32fe7ab7649c581d20686e8ced Reasons? Would reverting this commit be sufficient? Yes, that commit needs to be reverted at least. We will have to ship the directory in the root file. We should also consider updating vnstat because there are some new release available. Would you work on this, so we can ship this in Core Update 143? Update to 2.6, introducing the new 'vnstad'-daemon. Is running here since a few weeks - right now on Core 142. Patchwork: Patch 1/4 => https://patchwork.ipfire.org/patch/2926/ Patch 2/4 => https://patchwork.ipfire.org/patch/2923/ Patch 3/4 => https://patchwork.ipfire.org/patch/2924/ Patch 4/4 => https://patchwork.ipfire.org/patch/2925/ GIT: https://git.ipfire.org/?p=people/mfischer/ipfire-2.x.git;a=shortlog;h=refs/heads/vnstat I am setting this back to MODIFIED as the vnstat 2.6 patches just made it into next and will most likely be shipped with Core Update 145. |