On Fri, 25 Nov 2016, Jonah Naylor wrote:
I don't think nut is built with TCP wrappers support, although the
package is listed as depending on libwrap...
Why would you have such a dependency if nut didn't use TCP Wrappers?
I ran this command: ldd /sbin/upsd | grep libwrap.so and it has returned
no output.
If I run that command I get
maria:~ # ldd /usr/sbin/upsd
linux-vdso.so.1 (0x00007ffff8fa8000)
libssl.so.1.0.0 => /lib64/libssl.so.1.0.0 (0x00007f05a4ea6000)
libcrypto.so.1.0.0 => /lib64/libcrypto.so.1.0.0 (0x00007f05a4ab9000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f05a489b000)
libc.so.6 => /lib64/libc.so.6 (0x00007f05a44ed000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f05a42e9000)
libz.so.1 => /lib64/libz.so.1 (0x00007f05a40d3000)
/lib64/ld-linux-x86-64.so.2 (0x00007f05a510e000)
maria:~ #
No mention of libwrap, yet I have TCP wrappers compiled in.
Does this mean I have to compile from source or is there a way to add
the tcp wrapper support?
If your binary does not include TCP Wrappers, then you don't need to add
it, and you don't need /etc/hosts.allow. If your binary does include it,
you need /etc/hosts.allow. You don't have to have TCP Wrappers, and you
don't have to recompile.
Does your distribution have a mailing list which could answer the
configuration question?
Roger
_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
