[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: possible bug in ping -i implementation
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2018-08-25 17:36:55
Message-ID: CAK1hOcNjCR9E2L4pfN=S5jdrOFWhW2nUY1x0QC=-whpCxrhVUw () mail ! gmail ! com
[Download RAW message or body]

Fixed in git.
On Fri, Aug 17, 2018 at 4:26 PM Gianluigi Tiesi <sherpya@netfarm.it> wrote:
>
> On 08/15/2018 01:32 AM, Gianluigi Tiesi wrote:
> >
> > After 36d198ec6dc8f214a1e9122b993581613e6d7f12 ping stopped working on
> > android, now it calls ualarm instead of alarm, the default value for
> > interval_us becames 1 * 1000000
> >
> >
> > ualarm returns
> >
> > EINVAL usecs or interval is not smaller than 1000000.  (On systems where
> > that is considered an error.)
> >
> > same behavior using qemu-static
> >
> >
>
> if I understand ualarm (that uses setitimer) can be used only to wait a
> time < 1 second, so I suspect ping should use a different way to wait
>
>
>
> --
> Gianluigi Tiesi <sherpya@netfarm.it>
> EDP Project Leader
> Netfarm S.r.l. - http://www.netfarm.it/
> Free Software: http://oss.netfarm.it/
>
> Q: Because it reverses the logical flow of conversation.
> A: Why is putting a reply at the top of the message frowned upon?
> _______________________________________________
> busybox mailing list
> busybox@busybox.net
> http://lists.busybox.net/mailman/listinfo/busybox
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]