Xymon Mailing List Archive search

Xymon 4.3.x (including 4.3.25) on Solaris 10 SPARC w/libwrap installed

list Japheth Cleaver
Tue, 9 Feb 2016 14:19:57 -0800
Message-Id: <user-819d2be27da2@xymon.invalid>

Hi,

I'd wager rrdtool's package brings in libwrap for rrdcached access control
purposes. A little bit of Googling gives me
https://bugs.freedesktop.org/attachment.cgi?id=52504&action=edit , so
adding this to lib/xymonrrd.h would seem like it should work

/*
 * Solaris requires that the allow_severity and deny_severity
 * variables be defined in the client program.
 */
#ifdef __sun
extern int allow_severity;
extern int deny_severity;
#endif


A while back there had been discussion on adding libwrap as a compile time
option to xymond as a whole. If that were added in, this would probably be
taken care of.

Still strange that rrdtool pulls it in like that.

-jc


On Tue, February 9, 2016 1:07 pm, Ryan Novosielski wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Incidentally, a slightly differently crafted version of my query to
the mailing list brings up two other solutions:

http://lists.xymon.com/pipermail/xymon/2012-December/036431.html

Vernon Everett's solution was to try over again and it was "fixed by
magic," and Roland Soderstrom fixes this by moving /usr/ccs/bin/ld out
of the way while building (which is not something I'd consider doing;
not sure if removing /usr/ccs/bin from the PATH would work).

On 02/09/2016 03:14 PM, Ryan Novosielski wrote:
Hi there,

I brought his problem up ages ago
(http://lists.xymon.com/archive/2012-November/036102.html).
Basically, this happens when you do a make:

gcc  -o xymond_rrd  xymond_rrd.o       xymond_worker.o do_rrd.o
client_config.o ../lib/libxymontime.a -lrt ../lib/libxymoncomm.a
-L/usr/sfw/lib -lssl -lcrypto -lresolv -lsocket -lnsl -lrt
-L/opt/csw/lib -lrrd  -L/opt/csw/lib -lpcre Undefined first
referenced symbol                             in file deny_severity
/usr/sfw/lib/libwrap.so.1 allow_severity
/usr/sfw/lib/libwrap.so.1 ld: fatal: symbol referencing errors. No
output written to xymond_rrd collect2: ld returned 1 exit status
gmake[1]: *** [xymond_rrd] Error 1 gmake[1]: Leaving directory
`/root/src/xymon-4.3.25/xymond' gmake: *** [xymond-build] Error 2

A discussion of possible solutions for building is included in the
 above link.

Is there a better/more permanent solution that can be implemented
in the source code?

- --
____ *Note: UMDNJ is now Rutgers-Biomedical and Health Sciences*
|| \\UTGERS      |---------------------*O*---------------------
||_// Biomedical | Ryan Novosielski - Senior Technologist
|| \\ and Health | user-46c89e614701@xymon.invalid - 973/972.0922 (2x0922)
||  \\  Sciences | OIRT/High Perf & Res Comp - MSB C630, Newark
     `'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iEYEARECAAYFAla6VRUACgkQmb+gadEcsb5M9QCdFk+1VLNzbj7kzQWuKbErAwuu
SpUAoMHeTFW4VGe4hUZY43GD+7VsP8KN
=mxjs
-----END PGP SIGNATURE-----