David Kastrup writes:
>>> diff --git a/progress.c b/progress.c
>>> index 261314e..24df263 100644
>>> --- a/progress.c
>>> +++ b/progress.c
>>> @@ -66,8 +66,12 @@ static void set_progress_signal(void)
>>> static void clear_progress_signal(void)
>>> {
>>> struct itimerval v = {{0,},};
>>> +
On Wed, May 28, 2014 at 08:07:38PM +1200, Chris Packham wrote:
> On 28/05/14 18:14, Jeremiah Mahler wrote:
> > From signal(2)
> >
> > The behavior of signal() varies across UNIX versions, and has also var‐
> > ied historically across different versions of Linux. Avoid its use:
> > use si
Erik Faye-Lund writes:
> On Wed, May 28, 2014 at 10:19 AM, David Kastrup wrote:
>> Chris Packham writes:
>>
>>> On 28/05/14 18:14, Jeremiah Mahler wrote:
static void clear_progress_signal(void)
{
struct itimerval v = {{0,},};
+struct sigaction sa;
+
+
On Wed, May 28, 2014 at 10:19 AM, David Kastrup wrote:
> Chris Packham writes:
>
>> On 28/05/14 18:14, Jeremiah Mahler wrote:
>>> From signal(2)
>>>
>>> The behavior of signal() varies across UNIX versions, and has also var‐
>>> ied historically across different versions of Linux. Avoid it
Chris Packham writes:
> On 28/05/14 18:14, Jeremiah Mahler wrote:
>> From signal(2)
>>
>> The behavior of signal() varies across UNIX versions, and has also var‐
>> ied historically across different versions of Linux. Avoid its use:
>> use sigaction(2) instead. See Portability below.
On 28/05/14 18:14, Jeremiah Mahler wrote:
> From signal(2)
>
> The behavior of signal() varies across UNIX versions, and has also var‐
> ied historically across different versions of Linux. Avoid its use:
> use sigaction(2) instead. See Portability below.
Minor nit. The last sentence a
>From signal(2)
The behavior of signal() varies across UNIX versions, and has also var‐
ied historically across different versions of Linux. Avoid its use:
use sigaction(2) instead. See Portability below.
Replaced signal() with sigaction() in progress.c
Signed-off-by: Jeremiah Mahler
7 matches
Mail list logo
