[BusyBox] ping revision 1.51

[Tim Riker]

I tried it on the same binary, then patched, recompiled and tried again.

Musta been on drugs.

Well, the current it fine, so let's move on.

Erik Andersen wrote:
> 
> On Thu Jun 06, 2002 at 02:10:19PM -0600, Tim Riker wrote:
> > Hmm..
> >
> > I tested this and got the results I expected. It seems to be fine with
> > current cvs.
> >
> > I would run "./busybox ping -c 1 1.2.3.4 ; echo $?" and if 1.2.3.4 was
> > unreachable I'd still get a 0 back.
> >
> > Looked like the ping return was the issue, so I changed it. I retested
> > and I got the 1 return as I expected so I committed the change.
> >
> > The current CVS works just as expected. Was I on drugs? I had reports
> > from other busybox users of the same issue. Ping returning ok even if
> > the ping failed.
> >
> > Sorry for the hassle.
> 
> When I implemented the new config system and reorganized the
> busybox source tree, due to CVS limitations, I created a separate
> CVS tree, so now there is a "busybox.stable" tree and a "busybox"
> CVS tree.  Perhaps the ping bug exists in the "busybox.stable"
> tree (which is what is used on the tuxscreen) but you tried to
> fix that bug in the "busybox" CVS tree?
> 
>  -Erik
> 
> --
> Erik B. Andersen             http://codepoet-consulting.com/
> --This message was written using 73% post-consumer electrons--

-- 
Tim Riker - http://rikers.org/ - TimR at Debian.org
Lineo CTO - Tim at Lineo.com - http://www.Lineo.com/
BZFlag maintainer - http://BZFlag.org/ - for fun!