From: pille <pille@struction.de>
To: bluez-devel@lists.sourceforge.net
Subject: [Bluez-devel] l2ping seems to ignore -t timeout option
Date: Sun, 14 May 2006 17:39:52 +0200 [thread overview]
Message-ID: <44674F48.2060605@struction.de> (raw)
hi,
i noticed that l2ping does not care about the timeout-argument.
running a current l2ping from bluez-utils-2.25 against a device that's
not available timeouts after 20 seconds regardless of any -t parameter.
pitti ~ # time l2ping -c 1 00:01:02:03:04:05
Can't connect: Host is down
0.00s user 0.00s system 0% cpu 20.527 total
pitti ~ # time l2ping -c 1 -t 10 00:01:02:03:04:05
Can't connect: Host is down
0.00s user 0.00s system 0% cpu 20.509 total
pitti ~ # time l2ping -c 1 -t 20 00:01:02:03:04:05
Can't connect: Host is down
0.00s user 0.00s system 0% cpu 20.515 total
pitti ~ # time l2ping -c 1 -t 40 00:01:02:03:04:05
Can't connect: Host is down
0.00s user 0.00s system 0% cpu 20.521 total
pitti ~ # time l2ping -c 1 -t 80 00:01:02:03:04:05
Can't connect: Host is down
0.00s user 0.00s system 0% cpu 20.513 total
regards
pille
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next reply other threads:[~2006-05-14 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-14 15:39 pille [this message]
2006-05-16 14:15 ` [Bluez-devel] l2ping seems to ignore -t timeout option Fabien Chevalier
2006-05-16 14:35 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44674F48.2060605@struction.de \
--to=pille@struction.de \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.