statusmap.cgi can't find libgd.so.2 in /usr/local/lib

[Andreas Ericsson]

John Christian wrote:
> Hello,
> 
> I've RTFM, Googled, and checked the list archives but
> can't seem to really fix this issue. Any assistance
> would be very appreciated!
> 
> It seems that statusmap.cgi in nagios-plugins-1.4.1 is
> not finding libgd.so.2 in /usr/local/lib. If I copy
> libgd.so.2 from /usr/local/lib to /usr/lib,
> nagios-plugins finds it just fine and statusmap.cgi
> works fine.
> 
> How do I get nagios-plugins-1.4.1 to "see" the
> libgd.so.2 library in /usr/local/lib?
> 

echo /usr/local/lib >> /etc/ld.so.conf; ldconfig

> BTW: I did an ldd of all the Nagios CGI's and there
> are other CGI's that DO find other libraries in
> /usr/local/lib. For example, trends.cgi found
> libfreetype.so.6 in /usr/local/lib just fine. Seems
> strange that statusmap.cgi doesn't find what it needs
> in /usr/local/lib.
> 

Those were probably compiled with a static library location, or with 
/usr/local/lib added to the library path in the binary. Normally it just 
links to libc.so, for instance, and not /lib/libc.so. The dynamic 
link-loader takes care of looking in the configured path to find the 
proper library. This is good because it lets you run dynamically 
compiled binaries against a debugging library (for instance) without 
having to re-compile them.

-- 
Andreas Ericsson                   andreas.ericsson at op5.se
OP5 AB                             www.op5.se
Lead Developer


-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null