On Sun, 21 Aug 2005, Christophe Yayon wrote: > Hi again, > > I just upgraded again to FreeBSD5.4-Stable of August 20 and, i just > killed a nagios loop process which consume 100% of CPU... > The problem seems to persist again... > > How do think about this ? > Thanks in advance.
Go ask the nagios guys. If they are doing things after a fork() from a threaded application that are not allowed by POSIX, then they need to address it. > >> They choose to quote a weak reference to the actual requirement. > >> The standard says (in the fork() section): > >> > >> A process shall be created with a single thread. If a > >> multi-threaded process calls fork(), the new process shall > >> contain a replica of the calling thread and its entire address > >> space, possibly including the states of mutexes and other > >> resources. Consequently, to avoid errors, the child process may > >> only execute async-signal-safe operations until such time as one > >> of the exec functions is called. Fork handlers may be > >> established by means of the pthread_atfork() function in order > >> to maintain application invariants across fork() calls. -- DE _______________________________________________ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-hackers To unsubscribe, send any mail to "[EMAIL PROTECTED]"