Displaying 20 results from an estimated 700 matches similar to: "[nut] High level C and C++ libnutclient (#2)"
2015 Jul 06
4
Nut-2.7.3 & gcc-3.3.6
Dear developers,
libnutclient has been added as a C++ alternative to libupsclient in 2.7.1.
As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a
problem with nut-2.6.5.
Is it possible to add a configuration parameter like
'-without-libnutclient' to provide better compatibility with older gcc
versions please (since libnutclient is an alternative to
2015 Jul 06
4
Nut-2.7.3 & gcc-3.3.6
Dear developers,
libnutclient has been added as a C++ alternative to libupsclient in 2.7.1.
As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a
problem with nut-2.6.5.
Is it possible to add a configuration parameter like
'-without-libnutclient' to provide better compatibility with older gcc
versions please (since libnutclient is an alternative to
2012 Nov 10
1
libnutclient pull request
Hello all,
I come back to request comments (and merge) on my pull request of the
libnutclient.
https://github.com/clepple/nut/pull/2
All previous comments have been addressed (some fixes and documentation).
For memory, the libnutclient is an high-level C++ and C client library
allowing to dialog with upsd. The addressed model is oriented around
devices, variables and commands; unlike
2016 Dec 10
2
2.7.4 make install fails: libnutclient.so.0.0.0 missing
I upgraded an operating system to openSUSE 42.2, kernel 4.4 and recompiled
nut 2.7.4. ./configure, make clean and make went well, but make install
failed. Make reports
Making install in clients
make[1]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients'
make[2]: Entering directory '/mnt/home/rprice/nut/nut-2.7.4.dev/clients'
/usr/bin/mkdir -p '/usr/lib64'
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017 Apr 04
4
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk>:
> On 04/04/17 14.10, Roger Price wrote:
>
>> On Tue, 4 Apr 2017, Arnaud Quette wrote:
>>
>>
> [cuuuuut]
>
> Hi Arnaud, It seems to me that, looking out into the future, there are
>> three
>> things upsmon needs:
>>
>> 1. A fall-through <notify type> of
2015 Feb 13
1
Testing recommend, make Install error Re: Nut-upsuser Digest, Vol 116, Issue 10
Hi,
Thanks for help.
- I download the last version of NUT, 2.7.2.6
- I install library:
nss-devel
gcc-c++
So now I didn't get last errors on make.
But I get a new one when I try to do - make install
---------------------------
*[root at artesano nut-2.7.2.6]# make install*
Making install in include
make[1]: Entering directory `/home/artesano/Downloads/nut-2.7.2.6/include'
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
2007 Sep 11
2
Bug#439986: Renaming `UPSCONN' to `UPSCONN_t' causes problems when upgrading.
tags 439986 upstream
thanks
Hi Florian,
2007/8/29, Florian Forster <octo at verplant.org>:
> Package: nut-dev
> Version: 2.2.0-1
> Severity: minor
>
> After upgrading from version 2.0.something to version 2.2.0-1 the type
> `UPSCONN' had been renamed to `UPSCONN_t'. This is a problem for
> software that is supposed to work with different versions of this
>
2015 Jul 21
0
[Nut-upsuser] Nut-2.7.3 & gcc-3.3.6
2015-07-06 10:40 GMT+02:00 Sergey Talchuk <tals1975 at gmail.com>:
> Dear developers,
>
> libnutclient has been added as a C++ alternative to libupsclient in 2.7.1.
> As a result I can't compile nut 2.7.3 with gcc-3.3.6. There wasn't such a
> problem with nut-2.6.5.
>
> Is it possible to add a configuration parameter like
> '-without-libnutclient' to
2012 Oct 12
2
NSS support in trunk (was: NSS branch pull request)
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
2024 Dec 16
1
NUT on FBSD 14-2 fails to shut down UPS - select with socket: Invalid argument
I'm still digging into this but thought I'd post what I have so far in case
there's a known issue that's easily fixed.
I'm using the version of NUT that's in the ports tree (see the info at the
bottom). Using the SNMP drivers to talk with two ACP SmartUPSs.
NUT is functional about monitoring and initiating host shutdown. However,
when it comes time to shut down the UPSs
2022 Sep 16
1
Fwd: [networkupstools/nut] Hide 'Init SSL without certificate database' message for upsc (PR #1662)
On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote:
> Hello all,
> ? Here's a PR I want to ask community about: should NUT clients like upsc report (log!) or hide the infamous 'Init SSL without certificate
> database' message?
How should upsc be used in order to get SSL/TLS protection? There is no
configuration file with a CERTFILE declaration. Is there some other way
2022 Sep 16
1
Fwd: [networkupstools/nut] Hide 'Init SSL without certificate database' message for upsc (PR #1662)
On Fri, 16 Sep 2022, Jim Klimov via Nut-upsuser wrote:
> Hello all,
> ? Here's a PR I want to ask community about: should NUT clients like upsc report (log!) or hide the infamous 'Init SSL without certificate
> database' message?
How should upsc be used in order to get SSL/TLS protection? There is no
configuration file with a CERTFILE declaration. Is there some other way
2024 Dec 17
1
NUT on FBSD 14-2 fails to shut down UPS - select with socket: Invalid argument
Hello,
Thanks for the report and sorry about any complications.
A few first questions:
* is this setup known to have been working with earlier NUT releases (e.g.
same OS and devices, older NUT - can try with a custom build of older
tags)? Is this a regression, or we never knew the correct mappings for
timeouts and/or shutdown commands used by this model?
* is there the `select` error when
2014 Jan 15
3
Reviving the Windows port of NUT
Emilien,
just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again! We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows.
The problem is that we do not have a good branch in Git to work from. The windows_port branch got rebased, but since it has merge commits, it is a bit of a mess.
I apologize for
2012 Dec 10
0
libnutconf: An overview
?Hello fellow developers,
as you may have noticed from a few e-mails in the past,
there is a new NUT library in development these days.
It should be part of the NUT platform API in the future
and I'd like to present the status of work, hereby.
1/ The library shall be responsible of NUT configuration
management. It shall encapsulate access and manipulation
with all the configuration
2008 Jan 31
1
WBC subcomponents.
Hello
On Wed, 2008-01-23 at 00:10 +0300, Nikita Danilov wrote:
> Hello,
>
> below is a tentative list of tasks into which WBC effort can be
> sub-divided. I also provided a less exact list for the EPOCH component,
> and an incomplete list for the STL component.
>
> WBC tasks are estimated in lines-of-code with the total of (9100 + 3000)
> LOC, where LOC is a non-comment,
2014 Jan 15
0
Reviving the Windows port of NUT
2014/1/15 Charles Lepple <clepple at gmail.com>:
> Emilien,
>
> just saw your commit in Buildbot for testing some Windows changes. That's great that someone is working on this again!
> We have had a few users ask for updates to the 2.6.5+ version of NUT for Windows.
I am just fixing some bugs and implementing some minor
windows-specific features.
> The problem is that
2009 Jan 24
1
Patch to always install libupsclient-config
Hi,
when building with the WITH_DEV conditional, either `libupsclient.pc'
*or* `libupsclient-config' is installed. This is annoying when linking
with libupsclient, because you basically have to do the check twice,
once using `pkg-config' and once using `libupsclient-config'.
Please consider the attached patch, which changes the behavior of
`lib/Makefile.am' to install
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
2017 Apr 10
0
battery not installed, but battery still 100% and NUT 2.7.2-4 does not catch this and report a error
On 04/04/17 15.19, Arnaud Quette wrote:
>
>
> 2017-04-04 14:18 GMT+02:00 Jon Bendtsen <jon.bendtsen at jonix.dk
> <mailto:jon.bendtsen at jonix.dk>>:
[cuuuuut]
>
> there is a Github issue: https://github.com/networkupstools/nut/issues/415
> + a branch with the implementation:
> https://github.com/networkupstools/nut/tree/upsmon_alarm
>
> For now:
> -