Yes, the bug was about conversion of `upsdebugx()` and friends to macros,
so actual methods (and their parameter evaluations) only waste CPU cycles
when the verbosity level is high enough. Otherwise lots of logic was
executed to prepare method arguments only for it to bail out in the first
line.
On 7/5/23 03:17AM, Jim Klimov wrote:
Ah, I thought you missed in my earlier reply the part about a bug with debug printouts in 2.8.0 (fixed on master since),
did not comment on that when you replied with quoting... So, for now options are to bump debugging to 3+ or to build
your own in one of
Ah, I thought you missed in my earlier reply the part about a bug with
debug printouts in 2.8.0 (fixed on master since), did not comment on that
when you replied with quoting... So, for now options are to bump debugging
to 3+ or to build your own in one of many ways possible :\
On Wed, Jul 5,
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 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
=>
Upgraded to Debian bookworm - working nut system stopped working.
nut-server: Installed: 2.8.0-7
Trying :
/usr/lib/nut/upscode2 -a malaysia -DD
Network UPS Tools - UPScode II UPS driver 0.90 (2.8.0)
Warning: This is an experimental driver.
Some features may not function correctly.
10 matches
Mail list logo
