apr-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Garrett Rooney" <roo...@electricjellyfish.net>
Subject Re: apr_file operations returning system errno as apr_status_t
Date Sat, 03 Feb 2007 23:07:22 GMT
On 2/3/07, Nick Kew <nick@webthing.com> wrote:
> Someone on IRC #apache just reported a stupid error message:
>     (20014)Error string not specified yet: Error retrieving pid
>    file /var/run/apache2.pid
> I took a look at what could be causing it, and it appears to
> be down to apr_file_* functions returning an old-fashioned
> system errno as an apr_status_t value.  I haven't reproduced
> the user's reported error, but it comes from either
> apr_file_open or apr_file_read (via apr_file_read_full).
> Not sure how best to tackle this.  Is there some reasoning
> behind what errno numbers can be returned here?

I was under the impression that apr_status_t is a superset of errno,
so returning the current errno should be perfectly fine...


View raw message