similar to: C++ in NUT

Displaying 20 results from an estimated 10000 matches similar to: "C++ in NUT"

2024 Feb 06
0
Nut Server error
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner successfully started s6-rc: info: service base-addon-banner: starting ----------------------------------------------------------- Add-on: Network UPS Tools Manage battery backup (UPS) devices----------------------------------------------------------- Add-on version: 0.13.0 You are running the latest version
2015 Jul 06
2
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
Hi Charles, Thanks for the prompt reply! Errors occur when execute make: /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF $depbase.Tpo -c -o nutclient.lo nutclient.cpp &&\ mv -f $depbase.Tpo $depbase.Plo libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF .deps/nutclient.Tpo -c
2015 Jul 08
0
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
On Jul 6, 2015, at 10:32 AM, Sergey Talchuk <tals1975 at gmail.com> wrote: > /bin/sh ../libtool --tag=CXX --mode=compile g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF $depbase.Tpo -c -o nutclient.lo nutclient.cpp &&\ > mv -f $depbase.Tpo $depbase.Plo > libtool: compile: g++ -DHAVE_CONFIG_H -I. -I../include -MT nutclient.lo -MD -MP -MF
2015 Jul 08
1
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
Hi Charles, Yes, it looks like my g++ does contain STL library which might be just my specific case... However, as a temporary solution I disabled nutclient in Makefile (please find the file attached). And nut-2.7.3 can be compiled now. Thanks, Sergey On Wed, Jul 8, 2015 at 4:13 AM, Charles Lepple <clepple at gmail.com> wrote: > On Jul 6, 2015, at 10:32 AM, Sergey Talchuk
2012 Sep 05
2
[nut] High level C and C++ libnutclient (#2)
[I took the liberty of replying on nut-upsdev - not many people are using github yet since the NUT repository native format is still SVN.] On Sep 4, 2012, at 10:17 AM, Emilien Kia wrote: > This is a proposal for a new client library which scopes an higher level than the existing libupsclient. > > It needs less dependencies to be compiled than the libupsclient and can be easier to
2024 Nov 09
1
NUT stopped working after an upgrade
Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. I updated the system yesterday with all the latest Fedora packages. Now NUT will not run. Chasing the issue through the layers, I come to this: ===================== [root at mythtv rules.d]# upsc cyberpower Error: Driver not connected [root at mythtv rules.d]#
2016 Dec 03
3
Problem installing NUT on 16.04
On 12/03/2016 08:03 AM, Charles Lepple wrote: > On Dec 2, 2016, at 10:23 PM, Jack McGee <jack at greendesk.net> wrote: >> This is new install on Ubuntu 16.04, using packages from Synaptic, >> Network UPS Tools upsd 2.7.2 >> >> I am getting these messages in the terminal: >> Broadcast message from nut at amethi (somewhere) (Fri Dec 2 12:33:03 2016): >>
2017 Jun 19
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/18/2017 05:42 PM, Charles Lepple wrote: > On Jun 16, 2017, at 6:12 AM, Manuel Wolfshant > <wolfy at nobugconsulting.ro <mailto:wolfy at nobugconsulting.ro>> wrote: >> >> running autogen.sh was triggered automatically. but even if I do it >> explicitly, I still get: >> + autoreconf -i >> configure.ac:887: warning: AC_LANG_CONFTEST: no
2024 Nov 09
1
NUT stopped working after an upgrade
Did the upgrade by chance install/alter any udev rules causing the UPS devices to now have incorrect permissions? And what user is nut running as? On November 9, 2024 9:58:57 AM EST, Bill Gee <bgee at campercaver.net> wrote: >Running NUT version 2.8.2 on Fedora 40. NUT installed from the Fedora package. CyberPower CP1000AVRLCD connected by USB. > >I updated the system yesterday
2014 Sep 18
0
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > On 09/11/14 22:34, Charles Lepple wrote: >> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >> >>> I see a libusb_get_interrupt message in the log. Could that be the problem? >> Yes, it seems related. >> >> 1.126896 upsdrv_initinfo...
2017 Jun 19
2
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/19/2017 11:02 AM, Manuel Wolfshant wrote: > Thank a lot ! > Now, conclusions after attempting builds ( with no docs included since > attempting to enable them triggers the errors related to missing or > too old tools mentioned by me in an earlier message ) > - building against libsub 1.0 triggers the following 2 errors : > nutdrv_qx-nutdrv_qx.o: In function
2014 Sep 19
2
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On 09/17/14 22:31, Charles Lepple wrote: > On Sep 12, 2014, at 5:15 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> On 09/11/14 22:34, Charles Lepple wrote: >>> On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: >>> >>>> I see a libusb_get_interrupt message in the log. Could that be the problem? >>> Yes, it
2017 Jun 16
0
Unable to use nut-2.7.4 with Eaton 5E1500I USB
On 06/15/2017 04:32 PM, Arnaud Quette wrote: Hello > > .... still no reply from them ... > > is the guy you contacted Paul Henri? I wrote to a generic alias ( Ro-PQSupport ). Got a reply from a fellow Romanian who also CC:ed something looking like a list (List-EGPQCO-BUCRO-PQ ). I replied to both of them 5 days ago, received nothing since. > >>> Would you also
2024 Nov 09
1
NUT stopped working after an upgrade
Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS seeing the UPS at a low level. I looked through /dev/ but did not see a device that jumps out as the UPS. ===================== [root at mythtv rules.d]# dmesg | grep -i 0764 [ 2.021485] usb 1-1.8: New USB device found, idVendor=0764, idProduct=0501, bcdDevice= 0.01 [ 2.049515]
2024 Nov 10
2
NUT stopped working after an upgrade
Check /dev/hidraw6, as noted in your dmesg output (and any other *hid* devices under /dev). User nut has almost zero privs to devices unless a udev rule changes the perms on the dev for nut . . . On November 9, 2024 1:25:29 PM EST, Bill Gee <bgee at campercaver.net> wrote: >Nut should be running as user nut. As far as I can tell, the udev rules have not changed. And the system IS
2014 Sep 12
2
Nut 2.7.2 on OpenBSD 5.6 with APC USB UPS
On 09/11/14 22:34, Charles Lepple wrote: > On Sep 11, 2014, at 11:04 PM, Stan Gammons <sg063015 at gmail.com> wrote: > >> I see a libusb_get_interrupt message in the log. Could that be the problem? > Yes, it seems related. > > 1.126896 upsdrv_initinfo... > 1.126906 upsdrv_updateinfo... > 1.127023 libusb_get_interrupt: Function not implemented >
2013 Feb 27
1
[wmware][release] VMware ESXi Nut client 1.1.0 released
Hi, VMware nut client package has been updated to version 1.1.0 Change are : - upsmon and upsc updated to nut-2.6.5 - ups events are now on sent to vmware syslog New URL for package is : http://rene.margar.fr/downloads/NutClient-ESXi500-1.1.0.tar.gz Link on package from NUT website should be changed. Previous version (1.0.2) was downloaded 1334 times since 28/05/2012. Best regards, Ren?
2013 Apr 01
1
UPS nut and ESXi 5.0.0 UserVars not showing up
Hello nut-upsuser, I'm trying to configure nut to be used with esxi 5.0.0. I have a APC Back-ups xs1300 which im assuming is plugged into /dev/usb0205 but i could easily be wrong. lsusb gives me: Bus 02 Device 05: ID 051d:0002 American Power Conversion Uninterruptible Power Supply I am following the french blog post posted on the nut website under the vmware section. I downloaded the
2015 Sep 03
0
functional bug in code /clients/nutclient.cpp
On Sep 1, 2015, at 4:26 AM, Paul Vermeer <paul at elspaulnz.com> wrote: > > Hi nut users, (this is a re-send from the correct account) > > With pleasure, I have been using the code provided. Managed to get all working properly, except for the nutclient lib in C. As you have noticed, nutclient has a few rough edges. The original upsclient library has had a lot more testing,
2010 Oct 22
0
NUT and AsciiDoc (was: Next AsciiDoc release)
Hi Stuart, sorry for the lag in answering, I know that you're awaiting feedback for the final release... 2010/10/19 Stuart Rackham > Hi Arnaud > > I successfully compiled all the docs in svn:// > svn.debian.org/nut/branches/AsciiDoc using the current AsciiDoc trunk, and > yes, the chunked manual only has a single toc. But there was the added > problem of the article