On 7/4/23 10:01PM, Jim Klimov wrote:
Normally yes - enable and start the target and the particular services relevant
to your setup.
For the binary you have from packaging (if not rebuilt as suggested earlier), set debug_min=3 in ups.conf section for
upscode2, to currently trade driver
Normally yes - enable and start the target and the particular services
relevant to your setup.
For the binary you have from packaging (if not rebuilt as suggested
earlier), set debug_min=3 in ups.conf section for upscode2, to currently
trade driver viability for some storage traffic with more
Ok - I'm wondering is this is a systemd config bit?
systemctl restart nut-driver@malaysia.service
Job for nut-driver@malaysia.service failed because the control process exited
with error code.
See "systemctl status nut-driver@malaysia.service" and "journalctl -xeu
nut-driver@malaysia.service"
On 7/4/23 11:36AM, Tim Dawson wrote:
Is the omission of a leading slash *prior* to "bus' in the symlink realmor a
typo? IE:
# ll /dev/ttyUSB-nut
lrwxrwxrwx 1 root root 15 2023-07-03 20:20 /dev/ttyUSB-nut -> bus/usb/001/010
If real, the relative path will make link function dependent on
On 7/4/23 12:13, Karl Schmidt wrote:
On 7/4/23 05:31AM, Jim Klimov wrote:
Hello, thanks for the report and trying to wrap my head around it.
On a side note, it seems you've reported the same(?) UPS a couple of
decades ago? ;)
On 7/4/23 05:31AM, Jim Klimov wrote:
Hello, thanks for the report and trying to wrap my head around it.
On a side note, it seems you've reported the same(?) UPS a couple of decades
ago? ;)
https://networkupstools.org/networkupstools-master.github.io/ddl/Exide/NetUPS_SE_PRC2400a.html
Hello, thanks for the report and trying to wrap my head around it.
On a side note, it seems you've reported the same(?) UPS a couple of
decades ago? ;)
https://networkupstools.org/networkupstools-master.github.io/ddl/Exide/NetUPS_SE_PRC2400a.html
=>
