But yet again, in a manner inconsistent with what is most commomly seen.
*Consistency* across a platform (*nix, whatever) goes a long way, and doing
something differently out of arrogance, or just to be different it rather
nonsensical . . .
On April 30, 2024 3:43:01 PM EDT, Jim Klimov via
"why would anyone want to use "host:port" when "host port" works? That
just seems like "I want to rewrite the config format, because [why?]."
I see the host:port nomenclature in a *lot* of software, and the one thing it
gives is far easier parsing of multiple listen address:port pairs.
IE, to
(Bit by the goofy, only on this forum, reply-to add'r nonsense . . . sorry!)
Add an appropriate udev rule to give "nutty" access, or grant "nutty" the group
which has it already.
USB devices are *NOT* public by design.
- Tim
On February 28, 2024 12:13:33 PM EST, Jim Klimov via Nut-upsuser
"Is it possible I need to compile NUT myself instead of using the Ubuntu
package?"
Certainly! For me, it's very rare that I install anything that isn't compiled
from source.
As long as you have compilers and any prerequisite packages in place, it's
close to a trivial process.
- Tim
On
Unless I am completely missing something, I am not seeing a problem. If
upsd/upsmon shut down cleanly, the .pid files should *not* exist. Are they
creating correctly on startup? I don't see any errors indicating amproblem with
that . . . (and you don't say whether nutnruns or not).
On June 9,
Build it yourself! RPM is overrated, and almost always woefully behind current
release!
On April 5, 2023 6:55:14 PM CDT, Anthony Farrell
wrote:
>The current version of nut for EL8, nut-2.8.0-3 is broken since it came out in
>December
>2022.
>
>I have been waiting for an update to the RPM
My take is virtually silent in normal operation. A brief startup message, and
then nothing more that critical/fatal errors and major events/state changes. If
something happens, the user/admin can turn up debug to capture the next fault
(and if there isn't, then nothing to debug). Horrific
Either adjust the udev rules to create the tty devices with the desired
owner/perm, or add the nut user to the appropriate group to have access to the
device . . .Worst case, you can "brute force" by putting your chmod in rc.local
so it resets at boot (but that is pretty gross as solutions go .
23?
>
>The original suggestion was IIRC to
>
> telnet 192.168.1.235 3493
>
>from .236 and vive-versa to see if the upsd port (3493) is reachabl - so if
>clients on one Pi can see devices served by (connected to) the other.
>
>Am I missing sone context?
>Jim
>
>On Fri
It's been a very long time since I have seen a Linux distro enable telnetd to
allow telnet connections proper. Test using telnet to the nut port number
("telnet xxx.yyy.zzz.kkk portno") and see if that connects, or try somethhing
like ssh . . .
On February 17, 2022 11:39:41 AM CST, William
My thought was more to capture the battery voltage at the *exact*
instant that it drops . . .
Also, is there any difference if you test without NUT in the picture?
- Tim
On 08/17/2021 03:03 PM, Gene Heskett wrote:
On Tuesday 17 August 2021 14:12:10 Tim Dawson wrote:
Myself, I'd
Myself, I'd be in it with a meter when I tested. Quite often the sampling
intervals are too long on this type of stuff to catch quick events like this.
- Tim
On August 17, 2021 12:24:04 PM CDT, Manuel Wolfshant
wrote:
>On August 17, 2021 7:12:19 PM GMT+03:00, Gene Heskett
>wrote:
>>On
Is anyone else getting this Chinese crap trying to claim to be from the
NUT group?
In any case, not sure the group has much to do with it, but it's getting
mighty old . . .
- Tim
On 05/17/2021 01:50 PM, bsandersen dk wrote:
Greetings
Right here I direct you all the papers regarding our
Actually, su nut -c
Su asks for nothing if executed as root . . . it already knows it has
authority, so simply changes the user id the command is run as (as I recall,
with "-c" to run a script).
- Tim
On March 7, 2021 2:01:34 PM CST, Roger Price wrote:
>On Sun, 7 Mar 2021, Harlan Stenn wrote:
>
>> Why use sudo
Not to be abrasive, but why have you not installed libUSB and OpenSSL to enable
you to use NUT? Both are pretty trivial to install . . .
On January 28, 2021 10:09:53 AM CST, Alex Conway via Nut-upsuser
wrote:
>Hello,
>
>I'm a recent graduate and new hire at a company and I've been given what
I'm going to guess that since your test runtime of 305 is very close to the low
limit of 300, that's the warning. Not yet a fail, but very, very close.
On October 31, 2020 11:41:39 AM CDT, Rick Dicaire wrote:
>Hi folks, new to list...
>nut 2.7.2 on Ubuntu 16.04 with Cyberpowersystems
bian.net/cgi-bin/mailman/listinfo/nut-upsuser
--
Tim Dawson
972-567-9360
___
Nut-upsuser mailing list
Nut-upsuser@alioth-lists.debian.net
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
Wolfshant wrote:
On 8/12/20 8:10 AM, Tim Dawson wrote:
For directory permissions, the "x" priv determines if you can access
the directory, so going from 555 (r-x,r-x,r-x) to 640 (rw-,r--,---)
pretty much locks out access to the dir. Myself, I'd go back to 555.
640 essentially locks
Have you done a load/battery test without NUT running to see how long the UPS
will run? Not sure if yourngear will do it, but some UPS gear has an internal
battery test that will automate that process, without ever dropping output.
Also, how old are the batteries?
- Tim
On April 23, 2020
20 matches
Mail list logo
