[zeromq-dev] Meaning of: "Pgm-WARNING: peer expired"?

Martin Sustrik sustrik at 250bpm.com
Sat Oct 23 19:00:27 CEST 2010

On 10/20/2010 06:48 PM, Steven McCoy wrote:
> On 21 October 2010 00:21, Martin Sustrik <sustrik at 250bpm.com 
> <mailto:sustrik at 250bpm.com>> wrote:
>     How can I switch the messages off in 2.1?
> You can set PGM_MIN_LOG_LEVEL to FATAL,
> http://code.google.com/p/openpgm/wiki/OpenPgm5CReferenceErrorHandling

Looks like there's a way to plug in a log handler! Nice.

For now I can use a log handler that will just drop the messages.

In the future it would be nice if OpenPGM messages (at least some of 
them) were accessible via 0MQ logging system (sys:// transport). The 
problem I see is that there can be at most one loger function per 
process. That would break as soon as there are two 0MQ contexts in a 
process (say because the app is linking with two libraries, each of them 
using 0MQ). The loger function of the first context would be overwritten 
by the loger function of the second context, resulting in second context 
distributing its messages via the first context :(

Any idea how to solve this?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.zeromq.org/pipermail/zeromq-dev/attachments/20101023/c5f0ba85/attachment.html>

More information about the zeromq-dev mailing list