If you don't want your library behavior to be changed when process
receives some signals then you have to use such or some similar
approach.
Pavel
On Thu, Aug 18, 2011 at 9:38 AM, Stephan Beal <sgb...@googlemail.com> wrote:
> Hi, sqlite3 hackers,
>
> i'm taking a look at os_unix.c:
>
> do{ got = osPwrite(id->h, pBuf, cnt, offset); }while( got<0 && errno==EINTR
> );
>
> and i just have to ask: do you Unix signal experts out there (a group to
> which i do not belong, by the way) feel that this is a generically useful
> approach to solving the problem of an interrupted write()? i ask because i
> have a library in which i could really use this, but i don't know enough
> about the semantics of interrupted system calls to know if this is really a
> kosher general-purpose approach or if it's a questionable hack which we kids
> should not try at home.
>
> :-?
>
> --
> ----- stephan beal
> http://wanderinghorse.net/home/stephan/
> _______________________________________________
> sqlite-users mailing list
> sqlite-users@sqlite.org
> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
