Re: accept socket occasional read error

2020-02-29 Thread Bo Lorentsen
On 2/28/20 10:01 PM, Marc Lehmann wrote: That is confusing - if you read from the socket _without_ getting a readyness notification from libev, then of course you might get EAGAIN, but that wouldn't have anything to do with libev, as it isn't involved, right? This is by no means an libev error, b

Re: accept socket occasional read error

2020-02-24 Thread Bo Lorentsen
On 2/16/20 8:43 AM, Bo Lorentsen wrote: Hi ... Thanks for all your valuable input, I found the error at last, and the new version in my git spike is working as it should. The problem was starvation of my events and backlog overrun as a consequence, when the number of connections came in

Re: accept socket occasional read error

2020-02-18 Thread Bo Lorentsen
On 18.02.2020 12.24, Marc Lehmann wrote: > On Sun, Feb 16, 2020 at 08:43:20AM +0100, Bo Lorentsen wrote: >> I have a callback that gets called on every accept (where I loop on EAGAIN >> to empty the backlog), and for each new socket I make an protocol structure > You mean lo

Re: accept socket occasional read error

2020-02-17 Thread Bo Lorentsen
://localhost/ping I get from 0 - 200 length errors. I have keeps the logging to make things more easy to follow. Please let me know if you find anything interesting. /BL Den søn. 16. feb. 2020 kl. 11.37 skrev Bo Lorentsen : > On 2/16/20 9:08 AM, Bernd Petrovitsch wrote: > > Hi all! >

Re: accept socket occasional read error

2020-02-16 Thread Bo Lorentsen
On 2/16/20 9:08 AM, Bernd Petrovitsch wrote: Hi all! Thanks for taking you time to look into this, I really appreciate it. I have been using libev for a while in a project at work (currently 4.25), with success for quite a while, and I have now expanded the usage in our service to also include

accept socket occasional read error

2020-02-15 Thread Bo Lorentsen
Hi ... Sorry to write in this forum, but I have no idea as the where else to ask :-) I have been using libev for a while in a project at work (currently 4.25), with success for quite a while, and I have now expanded the usage in our service to also include the accepting of new connection (us

Re: C++11 lambda function

2017-07-22 Thread Bo Lorentsen
On 07/18/2017 10:28 AM, Bo Lorentsen wrote: > Hi ... > > First, thanks for a really useful event library, it is a really good > example in a minimalistic design. > > I have been using C++11 in production for a while, and I have been using > lambda functions too, with all the

C++11 lambda function

2017-07-18 Thread Bo Lorentsen
Hi ... First, thanks for a really useful event library, it is a really good example in a minimalistic design. I have been using C++11 in production for a while, and I have been using lambda functions too, with all the benefit this gives in the code layout. So I like to know if anyone have tried

Re: Mixing async and sync after a fork

2013-01-10 Thread Bo Lorentsen
On 01/10/2013 05:18 PM, Brandon Black wrote: On Thu, Jan 10, 2013 at 10:05 AM, Bo Lorentsen <mailto:b...@lue.dk>> wrote: The thing is ... this works amazingly, until I try to startup this app as a daemon (fork). And yes, when i start it as i daemon i make sure to call ev::

Mixing async and sync after a fork

2013-01-10 Thread Bo Lorentsen
Hi ... I have been playing with libev (ev++ in C++11) for a while now in a pure async setup for a while, and I have to say libev is a small but really nice peace of work, so thanks Mark :-) I needed to implement a set of long poll like function in some existing code base that uses, normal sy