[ On Thursday, October 11, 2001 at 20:06:18 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
cvs update
if [ $? -ne 0 ] ; then
echo something bad happened, exit status is $?
fi
exit $?
Neither of our scripts is truly useful because both always
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, October 12, 2001 9:11 AM
[ On Thursday, October 11, 2001 at 20:06:18 (-0700), Paul
Sander wrote: ]
And your point is what? That it's okay to sometimes let
nondeterministic
errors go undetected? Sorry, that's not good
--- Forwarded mail from Greg Woods:
[ On Thursday, October 11, 2001 at 20:06:18 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
And your point is what? That it's okay to sometimes let nondeterministic
errors go undetected? Sorry, that's not good enough.
I think in real life
[ On Wednesday, October 10, 2001 at 14:43:14 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
What happens on a Unix system when the exit status exceeds 127? It overflows.
Well, actually it'll depend on a number of factors. I suspect the
result is literally undefined from
--- Forwarded mail from Greg Woods:
[ On Wednesday, October 10, 2001 at 14:43:14 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
What happens on a Unix system when the exit status exceeds 127? It overflows.
Well, actually it'll depend on a number of factors. I suspect the
result
[ On Thursday, October 11, 2001 at 15:48:53 (-0700), Paul Sander wrote: ]
Subject: Re: cvs exit status
# Overflow occurs here; an exit status less than 258 indicates an overflow.
cvs update
echo exit status is $?
My code would say:
cvs update
if [ $? -ne 0
