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 p...@imatix.com wrote:
On Wed, Jun 27, 2012 at 3:43
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.f...@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
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
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 dacmor...@gmail.com wrote:
I run
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:);
zmq_connect(socket, epgm://eth0;224.0.0.1:);
even i place the eth0 with it's ip address
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:);
zmq_connect(socket, epgm://eth0;224.0.0.1:);
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
Ø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
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
On Friday, June 29, 2012 06:13:53 AM Paul Colomiets wrote:
On Thu, Jun 28, 2012 at 9:06 PM, Justin Karneges jus...@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
Anatoly,
The standard causes for memory exhaustion are, in order:
* You're forgetting to close messages, or doing it at the wrong time.
* Your consumer is unable to process messages at full speed, so the
queue builds up.
In the second case you need to decide how you want to handle the excess.
11 matches
Mail list logo
