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 differ
On Fri, Feb 11, 2011 at 4:28 PM, Alessio Sangalli wrote:
> Hi, I am using the owshell family of commands, usually from scripts; I
> usually capture the output of the command into a variable:
>
> sometimes for whatever reason - owread fails, maybe because owserver is
> not up (yet) or similar.
>
>
>
> -Original Message-
> From: Alessio Sangalli [mailto:ale...@manoweb.com]
> 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:
>
wfs-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 great
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 i
PHtest ] || [ $PHtest -gt 8 ]; then
echo "`date` PH reading error $PH" >>/var/scripts/nohup.out
PH="U"
fi
-Original Message-
From: Alessio Sangalli [mailto:ale...@manoweb.com]
Sent: Saturday, 12 February 2011 8:28 AM
To: OWFS (One-wire file system) discussion
Hi, I am using the owshell family of commands, usually from scripts; I
usually capture the output of the command into a variable:
temperature=$(owread /26.79D89100/temperature)
sometimes for whatever reason - owread fails, maybe because owserver is
not up (yet) or similar.
How do I detect
