similar to: Re: NUT docs bug & init-scripts for SuSE

Arjen, all I don't know if there is some prohibition against it, but the packages.html link for SuSE RPMs should be changed from: http://software.opensuse.org/ To something useful that will get the site visitors to the actual rpms. For the packages that were part of the distribution: http://download.opensuse.org/distribution/ or for updated packages on build service:

Hallo. Here is a simplification of the automake stuff for nut 2.2.2. The idea is simple: libcommon.a contains stuff for the binaries libparseconf.la contains stuff for binaries and shared library Both are NOINST, automake understands perfectly our intentions. The rest is only a removal of the implicitly defined stuff. On top of the parallel build patch I got build success on all platforms

I'm trying to Compile/Package and then (on a different box) Config/Run 2.8.1. Both boxes are Raspberry Pi 4b on Bullseye with a generic USB UPS. -- I'm trying to get nut running on my Raspberry (bullseye/11). (I'd also love to share a working 2.8.1 for Raspberry with the world, but...) I compiled the latest code from git: version 2.8.1-774-g963abbd87 I compiled it on one system

Ok - I'm wondering is this is a systemd config bit? systemctl restart nut-driver at malaysia.service Job for nut-driver at malaysia.service failed because the control process exited with error code. See "systemctl status nut-driver at malaysia.service" and "journalctl -xeu nut-driver at malaysia.service" for details. root at malaysia:~# systemctl status nut-driver at

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 logs :\ Sorry about that, Jim On Wed, Jul 5, 2023, 02:29 Karl Schmidt <karl at lrak.net> wrote:

I would like to keep NUT installed but disable it completely at times. I tried both 'disabling' and 'masking' all the following 'systemctl services nut-server nut-monitor nut-client ups-monitor nut-driver-enumerator as follows: systemctl disable nut-server nut-monitor nut-client ups-monitor nut-driver-enumerator systemctl mask nut-server nut-monitor nut-client

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 viability for some storage traffic with more logs :\ > > Sorry about?that, > Jim

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, 2023, 06:23 Karl Schmidt <karl at lrak.net> wrote: > On 7/4/23 10:01PM, Jim Klimov wrote: >

Dear Stanislav, thanks for your patch. The problem with your "recommended" pkgconfigdir is that in many cases, it does not work. Namely, when ${prefix} is not one of the standard places such as /usr. As I understand it, the whole point of a tool like pkgconfig is to allow other software to automatically detect the install location of NUT, especially when that location is not one of

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 many ways possible :\ I think I'm not following you - with debug 3 -->> it

Stan, I'm very pleased to see you back to work with us on enhancing nut in that many areas ;-) 2008/4/30 Stanislav Brabec <sbrabec at suse.cz>: > Stanislav Brabec wrote: > > > Please note that 2.2.2-pre3 installs hald addons by default to / on > > openSUSE 11.0 beta 2 x86_64. Not a big problem. > > Here is a patch, which fixes openSUSE 11.0 beta 2 x86_64:

https://bugs.freedesktop.org/show_bug.cgi?id=28891 Summary: [GeForce FX 5200] Broken KMS support (corrupted cursor) Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: minor Priority: medium Component: Driver/nouveau

Hi, I'm trying to get NUT running. I've installed it with pkg_add nut I can see my UPS as follows: # nut-scanner Cannot load SNMP library (libnetsnmp.so) : file not found. SNMP search disabled. Cannot load XML library (libneon.so) : file not found. XML search disabled. Cannot load AVAHI library (libavahi-client.so) : file not found. AVAHI search disabled. Scanning USB bus. No start

Hi David and fellows, I'm reviving this important thread about a common power management. To sum up, the first aim is to allow a better user experience on Linux by bridging NUT with Linux HAL, and Gnome Power Management / any PM GUI. But it also initiate a bigger investigation about how to integrate NUT support for UPSs into the native OS Power Management infrastructure for all supported

Hello, sorry and puzzled to hear about that. My guess would be permissions - while nut-scanner remains `root` (if started as one) and sees everything, drivers default to dropping privileges and may not see the devfs nodes (not sure OTOH which paths are involved on OpenBSD). One experimental workaround can be adding `user=root` to `ups.conf` entry for the device. But properly - tame whichever

All, Arnaud and I were discussing the *.spec files we have in the NUT source tree, and with the 2.4.0 release of NUT just around the corner, I would like to make sure we are pointing people in the right direction for NUT RPMs. Currently, we have *.spec files for "generic-rpm" (has a few macros for RedHat 6.x and 7.x), Mandriva (circa NUT 2.0.2), openSUSE, and RedHat (apparently from

2012/10/12 Emilien Kia <kiae.dev at gmail.com> > Hi guys, > Hi Emilien and the list, This is a pull request to finally merge NSS feature in nut trunk: > https://github.com/clepple/nut/pull/3 > I'd like to take a moment to shed some more light on this important development, which lasted 3 years: - the initial

Shamelessly reusing the announcement Arnaud sent about three months ago for nut-2.2.1: "We're preparing to release 2.2.1-pre2, so if you have some fixes to backport on Testing, consider announcing it and doing asap. As always, compatibilities update and bugfixes only!" Regards, Arjen -- Eindhoven - The Netherlands Key fingerprint - 66 4E 03 2C 9D B5 CB 9B 7A FE 7E C1

some notes: - for this kind of discussion, please cc upsdev list (I've added it), - I've fwded the full thread to upsdev, - this subject is part of what I call NUT-NG (next gen.), aka nut 3.0... - I'll study in depth the thread this week end, and complete with my thoughts, - thanks to Stan to have put us all in touch Arnaud 2006/3/10, Stanislav Brabec <sbrabec@suse.cz>: >

dear list, I am wondering if one can find examples and/or more detailed descriptions of modifications needed when going beyond standard corStruct classes (i.e. those already provided for use in lme/nlme)? When I looked at pages 238-239 of Pinheiro/Bates (2000): Mixed-effects models in S and S-plus, I found that I would need a bit more explicit guidance what to do for implementing a new