Re: accept() fails with EINTER

On Thu, 24 Feb 2005 [EMAIL PROTECTED] wrote: Trying to run an old server with a new kernel. A connection fails with "interrupted system call" as soon as a client attempts to connect. A trap in the code to continue works, but subsequent send() and recv() calls fail in the same way. Weren't you suppo

Re: accept() fails with EINTER

> Trying to run an old server with a new kernel. A connection > fails with "interrupted system call" as soon as a client > attempts to connect. A trap in the code to continue > works, but subsequent send() and recv() calls fail in > the same way. Weren't you supposed to just 'try again' when recei

Re: accept() fails with EINTER

linux-os wrote: Trying to run an old server with a new kernel. A connection fails with "interrupted system call" as soon as a client attempts to connect. A trap in the code to continue works, but subsequent send() and recv() calls fail in the same way. Anybody know how to mask that SIGIO (or whatev

accept() fails with EINTER

Trying to run an old server with a new kernel. A connection fails with "interrupted system call" as soon as a client attempts to connect. A trap in the code to continue works, but subsequent send() and recv() calls fail in the same way. Anybody know how to mask that SIGIO (or whatever signal)? Sett