Hello Paul,
On 9/27/2011 18:18, Paul Alfille wrote:
This has come up recently.
We currently scan very conservatively -- lots of retries with
different serial port settings and long timeouts. It's pretty slow for
an empty port. And there are several types of serial adapters (DS9097U
DS9097E LINK HA5 HA7S) each of which need specific testing.
When you say "we currently scan very conservatively" you mean that owfs
will eventually detect masters on /dev/ttyS? without having to specify
these in the owserver commandline? It seems that the commandline
requires at least one -d device, otherwise owserver will exit. Or are
you referring to the case where a bus master is removed from a known
port and then re-connected?
Scanning wouldn't be too hard, and it could probably be done in
parallel. Still, it's hard to find all potential port names. Any
suggestion?
Yes. A commandline which provides one or more port names to check.
Either in their full form or wildcard.
--scanport=/dev/ttyS1 /dev/ttyS2 /dev/ttyUSB0
Another helpful feature, based on a suggestion by [email protected] is to
run owserver with each port I wish to check. If it fails to load, then
the port does not have a bus master on it. So a commandline switch:
-- testport
would cause owserver to test for a master on the -d specifier and then
exit 0 if found or 1 if not.
/m
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Owfs-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/owfs-developers
