forked from vergoh/vnstat
-
Notifications
You must be signed in to change notification settings - Fork 0
/
INSTALL
132 lines (90 loc) · 4.38 KB
/
INSTALL
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
Compiling the binaries
::::::::::::::::::::::
This source package contains the required source files for vnStat including
the daemon (vnstatd) and image output (vnstati). Executing
./configure --prefix=/usr --sysconfdir=/etc && make
will compile 'vnstat' and 'vnstatd' without requiring additional libraries.
The optional image output capable binary 'vnstati' will also be compiled if
the required additional libgd2 library is found to be available. The
required extra packages are usually named libgd2 and libgd2-dev (or
libgd2-noxpm and libgd2-noxpm-dev in Debian/Ubuntu, xpm version can also
be used, libgd-dev in more recent releases).
An example cgi ('vnstat.cgi') to be used with http server with the image
output support has been provided in the 'examples' directory. Configuration
options for the cgi are in the beginning of the file.
Installing as root
::::::::::::::::::
Login as root and run the following command:
make install
If there were no errors, vnStat binaries, man pages and a config file
should now be installed. The configuration file will be upgraded
using previously configured values if it is found already to exist.
The configuration file /etc/vnstat.conf should also be checked at this
point. See the vnstat.conf man page for documentation about available
options.
Finally, make vnStat monitor available interfaces. Configure init scripts
so that the following command is executed once during system start:
vnstatd -d
The 'examples' directory contains suitable files for most commonly
used service managers:
systemd:
cp -v examples/systemd/vnstat.service /etc/systemd/system/
systemctl enable vnstat
systemctl start vnstat
upstart:
cp -v examples/upstart/vnstat.conf /etc/init/
initctl start vnstat
init.d:
Debian:
cp -v examples/init.d/debian/vnstat /etc/init.d/
update-rc.d vnstat defaults
service vnstat start
Red Hat / CentOS:
cp -v examples/init.d/redhat/vnstat /etc/init.d/
chkconfig vnstat on
service vnstat start
An alternative method is to just add the command to an already existing
script that gets executed during startup. In many distributions
/etc/rc.local can be used if nothing else suitable can be found.
During first startup, the daemon (vnstatd) should list and add all
available interfaces for monitoring. Depending on configuration, it may
take some minutes for the 'vnstat' command to begin showing results.
Monitoring of unwanted interfaces can be stopped with:
vnstat --delete -i ethunwanted
Installing without root access
::::::::::::::::::::::::::::::
Copy all needed binaries to some directory included in your PATH
(~/bin/ is an example) and make the database directory.
cp -v vnstat vnstatd vnstati ~/bin/
cp -v cfg/vnstat.conf ~/.vnstatrc
mkdir ~/.vnstat
Check that the binary got installed to a suitable location and is of the
correct version:
vnstat --version
If this gives 'command not found' then check content of your PATH variable.
The only way to fix a faulty kernel (afaik) is to compile/install a newer one.
This can't be done without the root account so you'll have to solve this
problem with your sysadmin if the kernel is broken.
Now open the config file ~/.vnstatrc with your favorite text editor and locate
the following line:
DatabaseDir "/var/lib/vnstat"
and replace it with
DatabaseDir "/pathtomyhomedir/.vnstat"
and save the file. If you are unsure about your home directory path, execute
cd ; pwd
The ouput should tell your home directory.
Now it's time to add a crontab entry for vnStat in order to get the daemon
running automatically after a system startup. Do that by executing the
command 'crontab -e' and add the following line (without leading spaces,
remember to change the path):
@reboot ~/bin/vnstatd -d
If you found yourself using a strange editor then 'man vi' should help.
Make sure the configuration file (~/.vnstatrc) has the log option either
disabled or set to a file that is located in a place where you have write
permissions, such as your home dir. Then try starting the daemon with
vnstat -d
After that wait for (or generate) at least 1024 bytes of network traffic
(and 5 min for the next database file save).
vnstat
Now you should get some stats about your network usage. See the config
file ~/.vnstatrc for interface and other settings.