$ diff /etc/vnstat.conf /etc/vnstat.conf.pacnew 1c1 < # vnStat 1.11 config file --- > # vnStat 1.12 config file 5c5 < Interface "enp3s0" --- > Interface "eth0" [snip] 93c105 < LogFile "/var/log/vnstat.log" --- > LogFile "/var/log/vnstat/vnstat.log" 96c108 < PidFile "/var/run/vnstat.pid" --- > PidFile "/var/run/vnstat/vnstat.pid"
Unlikely that on Arch Linux eth0 is more often used, than enp3s0. Does it makes any sense to place a log file into a directory?
Regards, Ralf
On 02-09-14 02:55, Ralf Mardorf wrote:
Unlikely that on Arch Linux eth0 is more often used, than enp3s0. Does it makes any sense to place a log file into a directory?
Regards, Ralf
From vnstat homepage : vnStat is a console-based network traffic monitor for Linux and BSD that keeps a log of network traffic for the selected interface(s).
the network interface names like enps30 are created by by systemd/udev , BSD uses other methods. Placing logfiles in /var/log makes perfect sense for every system that doesn't run systemd.
Also this .conf file is the one provided by upstream, and Arch Linux devs prefer a minimal patching approach, keeping packages as close to upstream as possible.
LW
Unlikely that on Arch Linux eth0 is more often used, than enp3s0.
I can't truly parse this sentence, but do you suggest the config file should use "enp3s0" ?
Because "enp3s0" depends on *your* hardware (it's the PCI bus 3, slot 0), and will be different on other computers (my laptop has enp2s0 and the desktop enp4s0)
arch-general@lists.archlinux.org