>On reciept of the info signal, the backends collaborate to piece >together a status file. The status file is given a temporay name. >When complete the status file is rename(2)'d over a well known >file. Reporting to files, particularly well known ones, could lead to race conditions. All in all, I think your better off passing messages through pipes or a similar communication method. I really liked the idea of a "server" that could parse/analyze data from multiple backends. My 2/100 worth... ---------------------------(end of broadcast)--------------------------- TIP 3: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to [EMAIL PROTECTED] so that your message can get through to the mailing list cleanly
- Re: [HACKERS] Performance monit... Samuel Sieb
- Re: [HACKERS] Performance monit... Tom Lane
- Re: [HACKERS] Performance monit... Bruce Momjian
- Re: [HACKERS] Performance monit... Tom Lane
- Re: [HACKERS] Performance monit... Bruce Momjian
- Re: [HACKERS] Performance monit... Tom Lane
- Re: [HACKERS] Performance monit... Bruce Momjian
- Re: [HACKERS] Performance monit... Jan Wieck
- Re: [HACKERS] Performance monit... Tom Lane
- Re: [HACKERS] Performance monit... Alfred Perlstein
- [HACKERS] Re: Performance monitor signal han... Thomas Swan
- [HACKERS] Re: Performance monitor signal... Alfred Perlstein
- Re: [HACKERS] Performance monitor signal handler Bruce Momjian
- Re: [HACKERS] Performance monitor signal handler Jan Wieck
- Re: [HACKERS] Performance monitor signal handler Jan Wieck
- Re: [HACKERS] Performance monitor signal handler Jan Wieck