Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 22 Aug 2005 08:53:57 +0400
From:      "Alexey Vesnin" <avesnin@mirknigi.ru>
To:        "Daniel Eischen" <deischen@freebsd.org>
Cc:        freebsd-hackers@freebsd.org
Subject:   Re: nagios and freebsd threads issue : help please ...
Message-ID:  <004301c5a6d5$811662e0$260210ac@win>
References:  <Pine.GSO.4.43.0508191502380.12955-100000@sea.ntplx.net>

next in thread | previous in thread | raw e-mail | index | archive | help

----- Original Message -----
From: "Daniel Eischen" <deischen@freebsd.org>
To: "Christophe Yayon" <lists@nbux.com>
Cc: <freebsd-hackers@freebsd.org>
Sent: Friday, August 19, 2005 11:03 PM
Subject: Re: nagios and freebsd threads issue : help please ...


> On Fri, 19 Aug 2005, Christophe Yayon wrote:
>
> > Hi all
> >
> > You should know about freebsd and nagios 2.0b threads issues (100% cpu
> > use by a forked process, lost check result, some pause of nagios main
> > process in certains obscursives conditions...).
> >
> > Some Nagios developpers says that the problem is in FreeBSD and some
> > other says that the problem is in nagios pthreads implementation, here a
> > resume of our discussions :
>
> See
http://www.freebsd.org/cgi/getmsg.cgi?fetch=340959+344806+/usr/local/www/db/
text/2005/freebsd-hackers/20050703.freebsd-hackers
>
> --
> DE
>
> _______________________________________________
> freebsd-hackers@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-hackers
> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe@freebsd.org"
>

This is a common problem with more common salvation : use ports/devel/pth
library. It will solve this problem COMPLETELY AT ALL. I'm currently running
FreeBSD-4-STABLE build, upgradin' my kernel weekly and has no sign of such a
problem. Always remember the main benefit of OpenSource - source is just a
subject to work with... You may use defaults and they must work, but there's
no guarantee that this will work fine and 100%-fast for YOUR
hardware/software environment. Don't be shy to make modifications -
developers aren't the ones who must do all the job for you. It's up toy you
personally.

Post Scriptum. 5.4 is not GOOD. It must be used ONLY if you don't have
another way. It's memory leak is horrible....




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004301c5a6d5$811662e0$260210ac>