-
Notifications
You must be signed in to change notification settings - Fork 71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vnstat --dumpdb #34
Comments
Any news? Does anyone have a patch for this? Any reactions what so ever? EDIT: Well, I ditched the vnstat-php-project, nothing seems to happen and when I started to re-write, I found vnstati which itself can give the same/or more extensive information I replaced it with vnstati and this php-code: exec('vnstati -s -i eno1 -o eno1_s.png', $vnstat); Then img source the files created... Matter closed for my part. |
Hello! Is it possible for more details please? Where should these lines be placed? |
Don't overwrite any existing files, create a new site on your webserver. |
i've created a fork that makes vnstat-php-frontend work with vnstat2 and the newly introduced |
A wrapper that reads the --json output and converts to --dumpdb lookalike. 1.modify config.php: 2.modify myvnstat.py: |
Hello,
I'm not sure how much are you maintaining this project.
vnstat from version 2.0 doesn't support command
vnstat --dumpdb
as it is currently required for your frontend to fill the data from vnstat.Here is the ticket and suggestion from
vnstat
maintainer: vergoh/vnstat#141Seems that the best option would be using command:
vnstat --json
which exports data to json format and then to parse it properly.
What is your opinion?
I know, you may answer - "well, try to fix it yourself" . Maybe, not sure/not much time at the moment.
Thanks.
All the best,
Frank
The text was updated successfully, but these errors were encountered: