On 02/12/2011 07:24 AM, Paul Alfille wrote: > You are right. There is no RETURN VALUE section of the man pages. > > What would you suggest? 0 for good, obviously, and 1 for error?
Yes this is absolutely reasonable; I am not sure if there would be the need for "finer" error reporting, like different values for each error condition. In case of error stdout or stderr could have a description associated with it if possible. The problem is that when I run the commands "interactively" I never run in this kind of error, that only happens in some cases when it's running for few days, or on reboot, etc. See my charts at: http://www.manoweb.com/alesan/webcam/report01.php When thre is NO VALUE the systen was disconnected, and that is ok, but when there are those values that go down to zero, that is a problem reading from the sensors with owfs. I would like to detect the error and not proceed with the "upload" of the "bogus" value. > All errors wouldn't be captured, like a bad 85C reading (although are > automatically repeated). But connection and memory allocation and bad > command line parameters would be easy to report. The first kind of error must be something where the calling script has some knowledge about the environment or the setup. The second one, is exactly, where it should be trivial to detect the problem. bye! as ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Owfs-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/owfs-developers
