ok that is stdout that is a temperature value, bogus or not. I was referring to the exit code, "$?" in bash.
bye as - - - - - > Sometimes the DS18B20 if its not communicating correctly returns 85, I do > not know the reason, it happened to myself a number of times when I first > setup some time ago. I have also read others getting 85 when its not > working correctly. > > The formatting of my script lost its <cr> however suppose you get the idea > of testing the returned value from owread via -z and >than what you believe > the value should be. > > > -----Original Message----- > From: Alessio Sangalli [mailto:[email protected]] > Sent: Saturday, 12 February 2011 2:17 PM > To: OWFS (One-wire file system) discussion and help > Subject: Re: [Owfs-developers] Exit code > > On 02/11/2011 02:14 PM, Robert Conway wrote: > > I use owread in my bash scripts, as I log in rrdtools if I find the > > data is not available I set the variable to "U" and send a message to > > nohup. I test for no data returned and if the value is greater than my > upper range. i.e. > > for DS18B20 if it comes back with the magical 85 it reports as an error. > > > So you do not use $? ?? And what is the magical 85? > > 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 > > > ------------------------------------------------------------------------------ > 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 > ------------------------------------------------------------------------------ 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
