Technically, not as the standard says that should not happen; though the <br>
thread may be woken up with the condition variable still false (spurious <br>
wake-up). That said, unfortunately, not all kernels obey that standard <br>
either by design or by bug from what I gleaned from the web. So, it&#39;s <br>
best to check for it anyway. However, even if you didn&#39;t check for EINTR, <br>
a wakeup for any reason (other than a plain immediate error) requires that <br>
you check the condition variable and if false re-issue the wait with a <br>
modified timeout (if so needed). So, there really is no reason to <br>
specifically test for EINTR as it&#39;s covered under the spurious wake-up <br>
rule.<br>
<br>
Andy<br>
<br>
On Tue, 6 May 2014, Lukasz Janyst wrote:<br>
<br>
&gt; Can `pthread_cond_timedwait` be interrupted by a signal handler? Exit with `EINTR`?<br>
&gt;<br>
&gt; ---<br>
&gt; Reply to this email directly or view it on GitHub:<br>
&gt; https://github.com/xrootd/xrootd/pull/111#issuecomment-42297677

<p style="font-size:small;-webkit-text-size-adjust:none;color:#666;">&mdash;<br>Reply to this email directly or <a href='https://github.com/xrootd/xrootd/pull/111#issuecomment-42324518'>view it on GitHub</a>.<img src='https://github.com/notifications/beacon/4118670__eyJzY29wZSI6Ik5ld3NpZXM6QmVhY29uIiwiZXhwaXJlcyI6MTcxNTAxMjQ4NiwiZGF0YSI6eyJpZCI6MzEyNjM3NTh9fQ==--8b8be44b4767e9be82483306cf8a731b6cc1e741.gif' height='1' width='1'></p>
<br>
<hr>
<p align="left">
Use REPLY-ALL to reply to list</p>
<p align="center">To unsubscribe from the XROOTD-DEV list, click the following link:<br>
<a href="https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1" target="_blank">https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=XROOTD-DEV&A=1</a>
</p>