On Wed, Jul 30, 2008 at 3:55 AM, Paul Alfille <[EMAIL PROTECTED]> wrote: > > s/non-blocking/blocking/ ?? Sorry, yes. The open() is now blocking (removed O_NONBLOCK) and the system is happy so far.
> > Should we still put a timeout on the writes? Especially if it's blocking? If open is changed to be blocking, I think write select/timeouts make sense. If the open is left non-blocking, I think the do/while retry loop would achieve a similar result (don't get stuck forever). As to which to go with, my inclination is to go with the non-blocking open and the do/while loop. It seems like owfs has been used successfully in a lot of different environments with the code the way it is. Just fixing the non-blocking writes seems like less risk to the user community. Perhaps others on the list could try the blocking open() and see how things work for them. Clearly I'm happy either way :) -- charles ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
