Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 01 Feb 2006 20:48:30 +0000
From:      Pete French <petefrench@ticketswitch.com>
To:        ivoras@fer.hr, peterjeremy@optushome.com.au
Cc:        freebsd-stable@freebsd.org
Subject:   Re: Restartable system call behaviour
Message-ID:  <E1F4Oty-000JEi-9R@dilbert.firstcallgroup.co.uk>
In-Reply-To: <43E10E44.1040502@fer.hr>

next in thread | previous in thread | raw e-mail | index | archive | help
> >>I have a piece of coode which does some networking, in which I see read
> >>and write calls failing with 'Interrupted system call' from time to time.
> > 
> > You will get EINTR if the interrupt occurs before any data is read
> > or written.
>
> Will it also happen with recv() with MSG_WAITALL flag set?

Actually I have narrowed this down now, and I wwas wrong in the original
posting - I was getting the EINTR returned by connect. Now I am not
sure if this is correct behaviour or not - if a signal has SA_RESTART set
then it should restart, but connect returns EINTR and then continues
to connect in the background.

I had alwways belived that if system calls are restrtable then you will never
see EINTR at all. Now I dont know if this is a problem with my understanding
of how the system works, or an actual bug. have filed a pr anyway, just in
case it *is* a bug.

-pcf.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1F4Oty-000JEi-9R>