similar to: [Fwd: Re: openSUSE 11.0 - NUT]

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:

I have been trying to get Nut working on a system with Fedora 8 i86_64 installed and an APC Smart-UPS USB. The 2.2.0 rpm does not seem to like the USB on this UPS. I have tried compiling the 2.2.2 version, from source, but am getting warnings. I have tried building it on my i386 system (f8 as well) and I get no warnings also the 2.2.0 works fine on that one with a TrippLite Omni 900 LCD via

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

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

Hi, i new on this list i don't know if this goes on development list or this list,? i have a ups Tripp Lite 750AVR(lusb info in the attach)? , i retrieve the current development tree from the subvervsion repo, and trying to compile NUT on Fedora8 to test the usb driver. the configure is ok: Configuration summary: enable SSL development code: yes enable IPv6 support: yes build

I can reproduce your list of missing files; I've written a make production to generate it. Something extremely odd is happening here. I looked at the first such case, clients/cgilib.h. When I grep for it in my generated nut.fi, I see this: grep -nH -e clients/cgilib.h nut.fi nut.fi:77309:M 100644 :14 clients/cgilib.h nut.fi:9602662:M 100644 :14 clients/cgilib.h nut.fi:10381358:M 100644 :14

On Mar 2, 2017, at 1:46 PM, Garrett Michael Hayes <Garrett at VerbalImaging.com> wrote: > > I would like to set up a Linux host as a central monitoring system for UPSs throughout our network. I?d like that system to be able to see the various UPSs basically in one of two ways: > 1) Tapping into a native network interface on the target UPS (such as some larger APC and

The attached patch is a first stab at adding 3phase support to upsstats/upsimage. I got a little carried away, so bare with me. This patch adds 3phase awareness to upsstats/upsimage and the template files, and in additional to the obvious 3phase variables: - upsstats: * Adds IF/ELSE-awareness, and since the parser logic is rather limited this means that we now have IF, ELSE IF etc since all

Hi, To to build an RPM from the nut 2.0.3 source I've corrected the old nut.spec.in file. Please find a copy of the slightly updated spec file attached. The changes are documented at the bottom of the spec file. Regards, Will -------------- next part -------------- # don't know how different I can do this %define majorver 2.0 %define version 2.0.3 %define relver 1 %define nutuser

Network UPS Tools version 2.4.3 has been released. http://www.networkupstools.org/ Note: this is only a bugfix release that only solves the regression on IPv6 activation. Direct access: - Download: http://www.networkupstools.org/source/2.4/nut-2.4.3.tar.gz - News: http://www.networkupstools.org/source/2.4/new-2.4.3.txt - ChangeLog: http://www.networkupstools.org/source/2.4/ChangeLog the NUT

Hi! Can someone with CVS write access please remove generated files from the CVS tree? The ones currently on my annoyance-list are: Makefile data/html/Makefile Also, the following files (+more, I only compile a subset of the drivers) should be added to .cvsignore in the corresponding directories (they're all generated): config.log config.status clients/Makefile clients/upsimage.cgi

I'll test it. I'm a bit confused with cgi-bin. I have made a lot of hosts.conf copies and didn't understand where does upsstats trying to find hosts.conf # ps -aux | grep ups _ups 13934 0.0 0.0 484 920 ?? Ss 5:41PM 0:01.53 /usr/local/bin/riello_ser -a senpro _ups 9171 0.0 0.1 532 1168 ?? Ss 5:41PM 0:00.13 /usr/local/sbin/upsd _ups 16906 0.0 0.1

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: > -

Citeren clepple+buildbot op ghz.cc: > The Buildbot has detected a new failure of FreeBSD-i686. > Full details are available at: > http://buildbot.ghz.cc/public/nut/FreeBSD-i686/builds/35 Charles, It seems that m4/nut_check_libhal.m4 fails to detect the proper path where to install the .fdi files. I have no idea where these files live on FreeBSD, so could you please find out what

hi- i'm using version 2.4.1, courtesy of debian testing, and noticed that in the web interface, the image for the battery voltage bar graph wasn't displaying. the other images (change, input, output, load) seem to be fine. the browser reports "500 internal server error", and apache reports "Premature end of script headers: upsimage.cgi, referer:

nut hardcodes systemdsystemshutdowndir to ${libdir}/systemd/system-shutdown. This is not valid: - Executable helpers are installed to ${libexecdir}, which is different from ${libdir} on bi-arch systems. - Even if nut will use ${libexecdir}, it could be different from systemd libexecdir. That is why it is better to check systemd.pc for the correct path. That path is stored as systemdutildir.

Hi, I've taken a small bit of time to initiate this work. There is now: - an m4 macro to detect the system (linux only ATM, but simple to complete) - a set of "make package" targets throughout the tree (limited to debian ATM) The remaining tasks on this specific point are: - m4 macro completion to handle all the supported platforms (at least the ones that have files in the

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

Hi all! I propose to replace the variables output.voltage.target.line and output.voltage.target.battery with the variable output.voltage.nominal. The reasons for doing it: * Unify naming, the term "nominal" is used both in NUT and by UPS makers for this. * Very few devices (none that I have seen) have a nominal output voltage that differs when on battery/mains. * A single