Project

General

Profile

Actions
Copy link

Bug #366

closed

Consumerd error socket race between fork and the thread managing it

Added by David Goulet about 12 years ago. Updated about 12 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
David Goulet
Target version:
LTTng - 2.1 stable
Start date:
10/10/2012
Due date:
% Done:

100%

Estimated time:

Description

We just witness, multiple times, a consumer being spawned and failing to connect to the error unix socket of the session daemon since the thread managing the consumer is spawned after the fork adding a very small windows where the connect fails with a permission denied since no listen() was done at the connect attempt.

This leads also to bug #365.

Actions
Copy link

Also available in: Atom PDF