[lttng-dev] libust "Error: Error opening shm" every ~4 seconds if HOME variable is not set
David OShea
David.OShea at quantum.com
Mon Nov 26 04:13:01 EST 2012
Hi Mathieu,
> -----Original Message-----
> From: Mathieu Desnoyers [mailto:mathieu.desnoyers at efficios.com]
> Sent: Tuesday, 30 October 2012 12:12 PM
> To: David OShea
> Cc: lttng-dev at lists.lttng.org
> Subject: Re: [lttng-dev] libust "Error: Error opening shm" every ~4
> seconds if HOME variable is not set
[...]
> Thanks for reporting! Can you try with stable-2.0 branch or master
> branch head ?
>
> Here are the commits:
>
> stable-2.0:
>
> commit e699eda9762d3cf3b0c40329eb3b6ce0947789dc
> Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> Date: Mon Oct 29 21:39:42 2012 -0400
>
> Cleanup: don't spawn per-user thread if HOME is not set
>
> Reported-by: David OShea <David.OShea at quantum.com>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
>
> master:
>
> commit 9ec6895c5633ed93c5acdf1e5b06f075fbd709d3
> Author: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
> Date: Mon Oct 29 21:39:42 2012 -0400
>
> Cleanup: don't spawn per-user thread if HOME is not set
>
> Reported-by: David OShea <David.OShea at quantum.com>
> Signed-off-by: Mathieu Desnoyers <mathieu.desnoyers at efficios.com>
Thanks for that! Patching e699eda into the 2.0.5 release fixed the issue.
Regards,
David
----------------------------------------------------------------------
The information contained in this transmission may be confidential. Any disclosure, copying, or further distribution of confidential information is not permitted unless such privilege is explicitly granted in writing by Quantum. Quantum reserves the right to have electronic communications, including email and attachments, sent across its networks filtered through anti virus and spam software programs and retain such messages in order to comply with applicable data security and retention requirements. Quantum is not responsible for the proper and complete transmission of the substance of this communication or for any delay in its receipt.
More information about the lttng-dev
mailing list