Now I've tested it, and it fixed the problem :)
Thanks,
Jimmy
On Tue, May 13, 2014 at 11:31 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Tue, May 13, 2014 at 07:40:53PM +0200, Umut Tezduyar Lindskog wrote:
It is also reproducible by just loosing the carrier on the link. Maybe
On Thu, May 15, 2014 at 10:40:48AM +0200, Jimmy Assarsson wrote:
Now I've tested it, and it fixed the problem :)
Great, thanks for testing. I'll push it to master then.
Zbyszek
On Tue, May 13, 2014 at 11:31 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Tue, May 13, 2014 at
Hi,
We will check it. Meanwhile, I believe you can also try it since
problem is arch independent. Just follow Jimmy Assarsson's
instructions.
Umut
On Tue, May 13, 2014 at 11:31 PM, Zbigniew Jędrzejewski-Szmek
zbys...@in.waw.pl wrote:
On Tue, May 13, 2014 at 07:40:53PM +0200, Umut Tezduyar
On Wed, May 14, 2014 at 09:05:12AM +0200, Umut Tezduyar Lindskog wrote:
Hi,
We will check it. Meanwhile,
Thanks.
I believe you can also try it since
problem is arch independent. Just follow Jimmy Assarsson's
instructions.
I know, I'm just being lazy :)
Zbyszek
It is also reproducible by just loosing the carrier on the link. Maybe new
async close is a candidate to solve it.
On Tuesday, April 29, 2014, Harald Hoyer harald.ho...@gmail.com wrote:
Am 28.04.2014 13:33, schrieb Jimmy Assarsson:
Hi,
We stumbled upon a freeze/block in systemd.
The
On Tue, May 13, 2014 at 07:40:53PM +0200, Umut Tezduyar Lindskog wrote:
It is also reproducible by just loosing the carrier on the link. Maybe new
async close is a candidate to solve it.
On Tuesday, April 29, 2014, Harald Hoyer harald.ho...@gmail.com wrote:
Am 28.04.2014 13:33, schrieb
Am 28.04.2014 13:33, schrieb Jimmy Assarsson:
Hi,
We stumbled upon a freeze/block in systemd.
The problem occurs when a rshd (socket activated) execution is completed, the
network connection is down and systemd is closing the socket.
This causes a long (60 seconds) freeze where it's not
Hi,
We stumbled upon a freeze/block in systemd.
The problem occurs when a rshd (socket activated) execution is completed, the
network connection is down and systemd is closing the socket.
This causes a long (60 seconds) freeze where it's not possible to communicate
with systemd.
Do you have any
