Return-Path: Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 26233 invoked by uid 500); 29 Oct 2001 21:08:44 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 26222 invoked from network); 29 Oct 2001 21:08:44 -0000 Date: Mon, 29 Oct 2001 13:08:47 -0800 (PST) From: Dirk-Willem van Gulik X-X-Sender: dirkx@titatovenaar.sfo.covalent.net To: dev@apr.apache.org Subject: EGAIN, EINTR et.al. Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Right now we are trapping EACCESS and moving it to 'EAGAIN' for a flock(). But on some platforms you can get things like EWOULDBLOCK and EINTR too. In APR is there a convenient macro to figure out if the exit code is a 'hard' error (say EINVAL, EBADF, ENOTSUPP) or one to figure out if it is a retryable type error ? Dw