Thanks. Probing in /proc sounds promising.
--Rob
Anthony DeRobertis wrote:
On Monday, October 21, 2002, at 12:51 PM, Rob Thorne wrote:
Manually, yes.
But is there any reasonable way to detect this programatically? I
need somehow to write a script that will detect the bad state and
then reinitialize the wireless interface.
Syslog can write to a pipe (at least a named one), your program can
read that and look for the message.
Also, if the interface error count starts going up (look at ifconfig)
you can read that out of /proc.
--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
--
Rob Thorne
Chief Technical Officer
Torenware Networks
--
general wireless list, a bawug thing <http://www.bawug.org/>
[un]subscribe: http://lists.bawug.org/mailman/listinfo/wireless
