PR# 13742 Many library routine calls in runtime don't check for errno == EINTR and retry

There are a large number of library routines called by the runtime which can
fail with errno == EINTR.  In such cases, the caller of the library routine
should check for errno == EINTR and retry the operation in this case
until it either succeeds or returns an errno value other than EINTR,
unless signals are blocked (really blocked, not via SIGBLOCK).  I believe
operations files on NFS-mounted file systems can fail with EINTR, depending
on how the the file systems are exported.  There are some places in the runtime
that already check for EINTR and react appropriately, but many places do not
check.

I recommend constructing (or hopefully finding on the web) a list of routines
that can fail with EINTR and then fixing all calls to these routines in
the runtime.

Here are some few specific examples of such routines:

        accept
        access
        chdir
        chmod
        chown
        close
        closedir
        cond_wait
        connect
        dup, dup2
        execl, execv, execle, excve, execlp, execvp
        fclose
        fcntl (with F_SETLKW or F_SETLKW64)
        fflush
        fgetc
        fopen, freopen
        fprintf
        fputc
        fread
        frtruncate
        fscanf
        fseek, fseeko
        fsync
        fwrite
        getgrnam, getgrgid, getgrent, fgetgrent, fgetgrent_r
        getmsg
        ioctl
        link
        nanosleep
        open
        pause
        poll
        printf
        putmsg
        read, readv, pwrite
        recv, recvfrom, recvmsg
        scanf
        select
        sem_wait, sema_wait
        semop, semtimedop
        send, sendto, sendmsg
        sigpause
        sigsuspend
        sigwait
        stat, lstat
        system
        truncate
        unlink
        ustat
        utimes
        wait
        waitpid
        write, writev, pwrite