On Jan 22, 2019, at 5:29 PM, NutList <[email protected]> wrote:
> 
> Hello all,
> I have exhausted my research and need a little help with some basic concepts. 
> First time configuration working with NUT and putting into a OS X 
> environment. Was able to install the package using Brew. Have read the 
> documentation and have been able to get the server running and agent running 
> using MACOSX-UPS driver and connect to UPS via USB. I would however like to 
> integrate a TrippLite UPS with TLNETCARD (IP management card). I see in the 
> documentation that this may be best accomplished using SNMP-UPS driver. 
> However, I do not see the SNMP-UPS drivers with the other drivers in the 
> directory of drivers? It is not clear to me if the Brew install does not 
> provide this driver or if I am missing something different in this concept? 
> Should there be an actual executable file named SNMP-UPS in the same 
> directory with the other drivers?

From <https://formulae.brew.sh/formula/nut 
<https://formulae.brew.sh/formula/nut>>, it looks like Brew does not enable 
SNMP support in NUT:

https://github.com/Homebrew/homebrew-core/blob/master/Formula/nut.rb#L52 
<https://github.com/Homebrew/homebrew-core/blob/master/Formula/nut.rb#L52>

I don't use Brew, so I am not sure if it is easier to adapt their configuration 
to compile against SNMP libraries, or if you can get Brew to coexist with Fink. 
The SNMP drivers for NUT are in the "nut-snmp" splitoff in Fink:

http://pdb.finkproject.org/pdb/package.php/nut-snmp 
<http://pdb.finkproject.org/pdb/package.php/nut-snmp>

I maintain the Fink package of NUT, so let me know if you have any questions. I 
have not tested against Mojave yet.

> I tried to look at the gist hub repos and dowloaded the snmp-ups (c and h) 
> files. When I try to make these under OS X 10.14,  I get the errors below. (I 
> must admit here that I am not great at making executables so this may be 
> something obvious that I am missing in the build). Seems strange to me there 
> would be this many errors in the current code base unless I have a bad 
> configuration parameter or the code is not compatible with Mojave?

The NUT source files are not meant to be compiled in isolation - the typical 
sequence is to run the "./configure" script to detect which versions of library 
functions are available (and where to find optional libraries), and then to run 
"make" (which will pass in a lot of extra preprocessor defines to the compiler 
with "-D"). You might be able to get Brew to show the details with some sort of 
"verbose" flag.

Please use reply-all to include the list (the list does not mangle headers like 
reply-to), and feel free to subscribe (it is not very high-traffic):

> Nut-upsuser mailing list
> [email protected]
> https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser

Reply via email to