vnstat2: fix all interfaces being monitored when none are configured
authorJan Hoffmann <jan@3e8.eu>
Thu, 21 Oct 2021 21:38:58 +0000 (23:38 +0200)
committerRosen Penev <rosenp@gmail.com>
Thu, 28 Oct 2021 08:31:18 +0000 (01:31 -0700)
commitecae7dedde0ccd2a636e93620ced41bca807d405
treee95efd05b22b47d2e628e131add66389642405ff
parentc1f4273501779e67ef88c7cbf0bbfcd24df16bc1
vnstat2: fix all interfaces being monitored when none are configured

By default, vnstatd adds all available interfaces on startup when its
database is empty. The --noadd option prevents this, but it breaks
import of legacy databases, and causes vnstatd to exit immediately
after startup, which breaks reloading.

This changes the init script to add the --noadd option when no legacy
databases need to be imported, and patches vnstatd to keep running
even when no interfaces are configured.

Signed-off-by: Jan Hoffmann <jan@3e8.eu>
net/vnstat2/Makefile
net/vnstat2/files/vnstat.init
net/vnstat2/patches/100-noexit.patch [new file with mode: 0644]