On Thursday, April 16, 2015, Jonas Thiem jonasth...@googlemail.com wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your lua is outdated, try lua 5.3 or at least lua 5.2.
Will do.
Meanwhile I made it to work with luajit, iy creates tun0 interfaces on both
machines, but cannot have ping
OK, will do.
On Tue, Apr 14, 2015 at 6:29 PM, Brian Knox bk...@digitalocean.com wrote:
That's great news Pieter. It is not urgent - the next rsyslog release will
be in ~ 4 to 5 weeks. If the next libzmq and czmq releases were in the same
time frame, that would be excellent.
Cheers,
Brian
Service requests are round-robined to available workers, as requests
or workers arrive. Requests are queued if there are no workers ready.
On Thu, Apr 16, 2015 at 4:15 AM, Kenneth Adam Miller
kennethadammil...@gmail.com wrote:
For malamute, are service requests dispatched per recipient client
It was never possible, due to the fact that pipes are being written
and read asynchronously. You cannot measure the free space except by
stopping everything.
The workaround is to use credit based flow control. I've a section in
the Guide that explains how this works. You can in effect know what %
Hello Pieter,
thank you for your answer.
I am in process of reading http://zguide.zeromq.org/hx:chapter7 , while atomic
counter seems more natural choice for inproc so far.
Could you please explain why it is possible to detect that we are at 100% of
HWM and it is not possible to detect that
At the point a message is placed on the queue it is either at HWM or has at
least space for one message, this can be evaluated atomically, claiming the
'slot' under the HWM for the message to be placed on the queue. Any other
threads attempting to send would synchronize with this operation and the
Thomas, Agree that it makes perfect sense for multiple producers and consumers, while in my case it is ZMQ_PAIR. Thanks. 17.04.2015, 16:49, "Thomas Rodgers" rodg...@twrodgers.com:At the point a message is placed on the queue it is either at HWM or has at least space for one message, this can be
Yes, this is true. If a sysadmin detects that a disk storage is 90% full, she notifies users and do other things to obtain more room, while it is quite possible that the disk is only 89% full at the moment.So, ability to calculate disk usage is "a likely source of confusion and gnashing of
Patches welcome.
On Friday, April 17, 2015, Ilja Golshtein ilej...@narod.ru wrote:
Yes, this is true.
If a sysadmin detects that a disk storage is 90% full, she notifies users
and do other things to obtain more room, while it is quite possible that
the disk is only 89% full at the moment.
This is an inquiry about the interface with ticket handlers and zloop.
I am running what I believe to be the latest development master of czmq
(downloaded Wed 2015/4/15 from github). My host is Ubuntu Linux 14.04LTS
running on a 64-bit Intel Core-i7.
Prior to this I had been running the
...
On Fri, Apr 17, 2015 at 5:12 PM, Thomas Rodgers rodg...@twrodgers.com wrote:
Patches welcome.
On Friday, April 17, 2015, Ilja Golshtein ilej...@narod.ru wrote:
Yes, this is true.
If a sysadmin detects that a disk storage is 90% full, she notifies users
and do other things to obtain
On Apr 17, 2015, at 10:00 AM, Ilja Golshtein ilej...@narod.ru wrote:
Agree that it makes perfect sense for multiple producers and consumers, while
in my case it is ZMQ_PAIR.
Simple solution for your use case:
Add an incrementing serial number to each of your outgoing messages.
The sending
I'm trying to get my first zactor implementation finished, compiled, and
debugged. I'm trying to create a zactor (and that seems to work OK).
Once the zactor has been created, I would like to include it in a zloop
reactor but I'm having trouble with type matchup in the following code:
*
13 matches
Mail list logo
