It really seems limited in that it can mainly give you the things you would see on the physical unit such as load etc.. wget https://downloads.sourceforge.net/project/apcupsd/apcupsd%20-%20Stable/3.14.14/apcupsd-3.14.14.tar.gz?r=https%3A%2F%2Fsourceforge.net%2Fprojects%2Fapcupsd%2Ffiles%2Flatest%2Fdownload&ts=1598115866 tar -zxvf apcupsd-3.14.14.tar.gz cd apcupsd-3.14.14 [root@somebox apcupsd-3.14.14]# ./conf........

I've encountered this problem before and I believe it may affect other drivers (I could test but I don't have time). This was happening on my custom Linux system with the pcnet32 driver. pcnet32: eth0: transmit timed out, status 97fb, resetting (and some other kernel module tracing in dmesg) Basically it means the card is connected (it shows connected in full duplex etc.. and recognized if the cable is disconnected too) but no packets can be sent or received........

Igot this after copying a VMWare image onto another machine in Debian. SIOCSIFADDR No such device eth0 error while getting interface flags The solution 1.) Find and edit the device line in persisent-net.rules note it will be prefixed with something like z25 or something else. vi /etc/udev/rules.d/z25_persistent-net.rules The easiest way is to comment anything out. If you are feeling........