Recurring Problem
Not enough info is given with ports installations or pre-installs
(not so bad in 2004 with 9000 ports avail.)
a minor problem here, but it keeps me from suggesting FreeBSD a lot.
...
examples (my other large list is put away somewhere)
...I have installed amaya, but it is
i386, very current
nagios 2.11
after portupgrade, a nagios which used to work fine now does
---
# /usr/local/etc/rc.d/nagios start
Performing sanity check of nagios configuration: FAILED
Nagios 2.11
Copyright (c) 1999-2007 Ethan Galstad (http://www.nagios.org)
Last Modified: 03-12-2008
Current FreeBSD problem reports
The following is a listing of current problems submitted by FreeBSD users.
These represent problem reports covering all versions including\nexperimental
development code and obsolete releases.\n
Bugs can be in one of several states:
o - open
A problem report has
Did this include an upgrade of Nagios or has the upgrade of a dependent
resulted in this?
not sure
Starting on line 1, hmm... Sounds like the files are being read twice,
what does nagios.cfg have to say for itself?
# grep cfg nagios.cfg | grep -v ^#
# grep cfg nagios.cfg | grep -v ^#
cfg_file=/usr/local/etc/nagios/commands.cfg
cfg_file=/usr/local/etc/nagios/localhost.cfg
cfg_file=/usr/local/etc/nagios/contactgroups.cfg
cfg_file=/usr/local/etc/nagios/contacts.cfg
cfg_file=/usr/local/etc/nagios/hostgroups.cfg
On 12/05/2008, at 8:53 PM, Randy Bush wrote:
Did this include an upgrade of Nagios or has the upgrade of a
dependent
resulted in this?
not sure
Nagios 2.11 was committed about six weeks ago for memory, though
reading further I think it was actually the trigger.
Starting on line 1,
On 12/05/2008, at 8:33 PM, Randy Bush wrote:
i386, very current
nagios 2.11
after portupgrade, a nagios which used to work fine now does
Did this include an upgrade of Nagios or has the upgrade of a
dependent resulted in this?
# /usr/local/etc/rc.d/nagios start
Performing sanity check of
Dear Kent
Sorry for the delay but I was very busy in the past days.
2008/4/28, Kent Stewart [EMAIL PROTECTED]:
After successfully update to FreeBSD 7.0 (a described in the
handbook) I startet several times portupgrade -faP after several
pkgdb -F. But now I get the following error:
Some ports of mine are awaiting commit for almost a month. Someone has
taken responsibility. But it seems the task has been neglected.
Is there some way to change the responsible back to Ports in hope of
finding another committer?
___
There is a problem during the build of the package using portsnap because
libxml2 is built 2 times, one before mod_security's installation (this one
is ok) and one other after mod_security's installation (this one makes an
error because libxml is already installed).
Best Regards,
--
Fabien
On Mon, May 12, 2008 at 06:58:18PM +0200, Dominic Fandrey wrote:
Some ports of mine are awaiting commit for almost a month. Someone has
taken responsibility. But it seems the task has been neglected.
Is there some way to change the responsible back to Ports in hope of
finding another
On 04/30/2008 11:35, Jason Evans wrote:
Eric Schuele wrote:
On 04/28/2008 16:31, Jason Evans wrote:
What is liblthread?
linuxthreads, as Mezz mentioned.
It looks to be interacting badly with malloc.
ok. any thoughts as to why, or how to fix it?
Most likely, the linuxthreads port is
12 matches
Mail list logo
