FreeBSD & Nagios with statusmap.cgi | How??

[Stanley Hopcroft]

Dear Sir,

I am writing to say that Nag-1.0 works fine on my FreeBSD 4.7-RELEASE
host.

I suggest that 

1 If you don't like building from source, let pkg_add worry about the
dependencies

2 that configure doesn't find gd on every version of FreeBSD that
Netsaint or Nag has run on (3.x onward).

Here's my configure options

tsitc> head build/nagios-1.0/config.status
#! /bin/sh
# Generated automatically by configure.
# Run this file to recreate the current configuration.
# This directory was configured as follows,
# on host tsitc.aipo.gov.au:
#
# ./configure  --with-gd-inc=/usr/local/include/gd
--with-gd-lib=/usr/local/lib --enable-embedded-perl --with-perlcache
--enable-DEBUG3
#
# Compiler output produced by configure, useful for debugging
# configure, is in ./config.log if it exists.
tsitc> 

The gd stuff was installed from the FreeBSD packages, gd-1.8.4_6 I think
(can't say for sure because I have damaged/trashed my package database).

HTH,

Yours sincerely.



-- 
------------------------------------------------------------------------
Stanley Hopcroft
------------------------------------------------------------------------

'...No man is an island, entire of itself; every man is a piece of the
continent, a part of the main. If a clod be washed away by the sea,
Europe is the less, as well as if a promontory were, as well as if a
manor of thy friend's or of thine own were. Any man's death diminishes
me, because I am involved in mankind; and therefore never send to know
for whom the bell tolls; it tolls for thee...'

from Meditation 17, J Donne.


-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
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