Am Samstag, 9. Mai 2009 schrieb Jan Kandziora: > > To my curiosity, today it works as expected. What the heck...? If anyone > could explain from the log what went wrong yesterday, I'd be very happy. > I think I have it now:
If one is reading the alarm/ directory and no chip is in alarm state, OWFS
returns EIO. owtcl returns that EIO instead of an empty reply. Is that
expected behavior? I would find it more useful to have an empty reply to
distinguish from "real I/O errors".
Kind regards
Jan
--
...very few phenomena can pull someone out of Deep Hack Mode, with two
noted exceptions: being struck by lightning, or worse, your *computer*
being struck by lightning.
-- Matt Welsh
signature.asc
Description: This is a digitally signed message part.
------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
