Feng Shuo | 2 Jul 09:56 2012
Picon

Re: OpenSUSE Build Service for ZeroMQ

Hi Pieter,


I created the page at http://www.zeromq.org/distro:opensuse. Since I'm not a native English speaker, I'm very happy if anyone could review the page and fix any grammar issues. :-)

On Thu, Jun 28, 2012 at 4:04 PM, Pieter Hintjens <ph <at> imatix.com> wrote:
On Wed, Jun 27, 2012 at 3:43 PM, Feng Shuo <steve.shuo.feng <at> gmail.com> wrote:

> Just an update. I create two upstream builds in the OBS by it's "git source"
> service. Whenever there is a commit, OBS will pull the updates and do a on
> all platforms...

Nice. On the http://www.zeromq.org/community page there is a section
for builds and distros, and you might add an OpenSUSE page here
(http://zeromq.distro:opensuse).

-Pieter
_______________________________________________
zeromq-dev mailing list
zeromq-dev <at> lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev



--
Feng Shuo
Tel: (86)10-59851155-2116
Fax: (86)10-59851155-2008
Tianjin Zhongke Blue Whale Information Technologies Co., Ltd
10th Floor, Tower A, The GATE building, No. 19 Zhong-guan-cun Avenue
Haidian District, Beijing, China
Postcode 100080

_______________________________________________
zeromq-dev mailing list
zeromq-dev <at> lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Pieter Hintjens | 2 Jul 12:02 2012

Re: OpenSUSE Build Service for ZeroMQ

Steve,

Looks great, and I didn't see a single spelling or grammar issue... :)

-Pieter

On Mon, Jul 2, 2012 at 4:56 PM, Feng Shuo <steve.shuo.feng <at> gmail.com> wrote:

> I created the page at http://www.zeromq.org/distro:opensuse. Since I'm not a
> native English speaker, I'm very happy if anyone could review the page and
> fix any grammar issues. :-)
Daniel Morton | 2 Jul 17:09 2012
Picon

Make Install Error

I run ./configure and make seemingly without incident; 
make check passes all 9 tests but when I run make 
install I get the following error message:

Making install in src
test -z "/usr/local/lib" || ../config/install-sh -c -d "/usr/local/lib"
/bin/sh ../libtool --mode=install /usr/bin/install -c  libzmq.la '/usr/local/lib'
libtool: install:
/usr/bin/install -c .libs/libzmq.1.dylib /usr/local/lib/libzmq.1.dylib
install: /usr/local/lib/libzmq.1.dylib: Permission denied
make[2]: *** [install-libLTLIBRARIES] Error 71
make[1]: *** [install-am] Error 2
make: *** [install-recursive] Error 1

What isn't working?
Michel Pelletier | 2 Jul 17:45 2012
Picon

Re: Make Install Error

By default make install installs to /usr/local which requires root permissions.

You can either run make install as root or pass
"--prefix=/different/path" to configure to install it to a different
path.

-Michel

On Mon, Jul 2, 2012 at 8:09 AM, Daniel Morton <dacmorton <at> gmail.com> wrote:
> I run ./configure and make seemingly without incident;
> make check passes all 9 tests but when I run make
> install I get the following error message:
>
>
> Making install in src
> test -z "/usr/local/lib" || ../config/install-sh -c -d "/usr/local/lib"
> /bin/sh ../libtool --mode=install /usr/bin/install -c  libzmq.la '/usr/local/lib'
> libtool: install:
> /usr/bin/install -c .libs/libzmq.1.dylib /usr/local/lib/libzmq.1.dylib
> install: /usr/local/lib/libzmq.1.dylib: Permission denied
> make[2]: *** [install-libLTLIBRARIES] Error 71
> make[1]: *** [install-am] Error 2
> make: *** [install-recursive] Error 1
>
> What isn't working?
>
> _______________________________________________
> zeromq-dev mailing list
> zeromq-dev <at> lists.zeromq.org
> http://lists.zeromq.org/mailman/listinfo/zeromq-dev
邱敏鈴 | 2 Jul 12:19 2012
Picon

zeromq epgm transport cannot work

hi~


There are some problems when i use the zeromq epgm transport.

My system is ubuntu 12.04.

I have built the source with --with-pgm option.

Problem 1:

zmq_bind(socket, "epgm://eth0;224.0.0.1:5555");
zmq_connect(socket, "epgm://eth0;224.0.0.1:5555");

even i place the eth0 with it's ip address but both sides have error message:

Assertion failed: res != NULL (pgm_socket.cpp:137)
Abort (core dumped)

Problem 2:

zmq_bind(socket, "epgm://*;224.0.0.1:5555");
zmq_connect(socket, "epgm://*;224.0.0.1:5555")

There are no error message but the receiver side doesn't receive any messages.

Please help me. I don't know what's wrong. 

Thanks.
_______________________________________________
zeromq-dev mailing list
zeromq-dev <at> lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Steven McCoy | 2 Jul 19:13 2012
Picon

Re: zeromq epgm transport cannot work

On Monday, 2 July 2012, 邱敏鈴 wrote:

hi~

There are some problems when i use the zeromq epgm transport.

My system is ubuntu 12.04.

I have built the source with --with-pgm option.

Problem 1:

zmq_bind(socket, "epgm://eth0;224.0.0.1:5555");
zmq_connect(socket, "epgm://eth0;224.0.0.1:5555");

even i place the eth0 with it's ip address but both sides have error message:

Assertion failed: res != NULL (pgm_socket.cpp:137)
Abort (core dumped)

Problem 2:

zmq_bind(socket, "epgm://*;224.0.0.1:5555");
zmq_connect(socket, "epgm://*;224.0.0.1:5555")

There are no error message but the receiver side doesn't receive any messages.

Please help me. I don't know what's wrong. 

Thanks.
 
If this is the 3.x release candidate please try git head instead.  This is a known and resolved defect.

-- 
Steve-o
_______________________________________________
zeromq-dev mailing list
zeromq-dev <at> lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Chuck Remes | 2 Jul 20:48 2012

daily build cluster question

I see on the #zeromq.build channel that the ffi-rzmq gem has failures on Debian linux. I'm the maintainer of
that gem and would like to fix those failures. On my OSX box *and* my Archlinux box, the specs all pass. What
version of Debian Linux (3, 4, 5 or 6) should I install to match the build cluster so I can reproduce this problem?

cr
Anatoly | 2 Jul 20:48 2012
Picon

Releasing RAM in Chunks

ØMQ Crowd,

    Reading messages from a socket, placing them on the zmq (PUSH). On the other side reading messages of off the queue (PULL) and persisting them in to DB. 

    If we get millions of messages, ØMQ takes X GB of RAM (since the pushing in this case is at much higher speed than pulling that waits for a DB for each pull), and does not release these Gigs until ALL of the messages are consumed (e.g. pulled). 

    Is there a way to configure it to release memory in chunks as the queue is being emptied?

Thank you,
/Anatoly
_______________________________________________
zeromq-dev mailing list
zeromq-dev <at> lists.zeromq.org
http://lists.zeromq.org/mailman/listinfo/zeromq-dev
Chuck Remes | 2 Jul 20:53 2012

Re: Releasing RAM in Chunks

On Jul 2, 2012, at 1:48 PM, Anatoly wrote:

> ØMQ Crowd,
> 
>     Reading messages from a socket, placing them on the zmq (PUSH). On the other side reading messages of off
the queue (PULL) and persisting them in to DB. 
> 
>     If we get millions of messages, ØMQ takes X GB of RAM (since the pushing in this case is at much higher speed
than pulling that waits for a DB for each pull), and does not release these Gigs until ALL of the messages are
consumed (e.g. pulled). 
> 
>     Is there a way to configure it to release memory in chunks as the queue is being emptied?

What you have posted should not be true. The memory for a message will be released when you call
zmq_msg_close(). If you are making that call and the memory isn't freed, then there is a bug. See the man
page at http://api.zeromq.org/2-2:zmq-msg-close

If you see something different, then please provide an example (written in C) that demonstrates the
problem and open a bug. Thank you.

cr
Justin Karneges | 2 Jul 21:57 2012

Re: HWM behaviour & blocking

On Friday, June 29, 2012 06:13:53 AM Paul Colomiets wrote:
> On Thu, Jun 28, 2012 at 9:06 PM, Justin Karneges <justin <at> affinix.com> wrote:
> > It's really just for functional completeness of my event-driven wrapper.
> > The only time I can see this coming up in practice is an application
> > that pushes a message just before exiting.
> > 
> > For now, I set ZMQ_LINGER to 0 when a socket object is destroyed, making
> > the above application impossible to create. What I'm thinking of doing
> > now is offering an alternate, blocking-based shutdown method. This would
> > violate the spirit of my wrapper, but may work well enough for apps that
> > finish with a single socket doing a write-and-exit.
> 
> I think you should just set linger and use it. zmq_close() doesn't
> block. The zmq_term() blocks.

Wow, silly me working around a non-problem. I was assuming zmq_close() 
blocked. Thanks for clarifying.

Justin

Gmane