2012/10/17 Jan Stary <h...@stare.cz>: > This is current/i386 on an IBM Thinkpad T40. > > It comes with an ipw(4) wifi interface, which works fine. Anyway, > the ipw(4) seems to be one of the substantial battery eaters. So > I would like to not use the interface when running on battery > and not actually using a wifi connection. > > Running 'ifconfig ipw0 down' seems to do that: the antenna icon led > switches off, and time left (as reported by apm) starts increasing. > (What would be a more rigorous way to see that the battery is actually > running off more slowly now, others being equal? The machine doesn't > have any sensors, as reported by 'sysctl hw'). > > I would like to let that happen automatically, if only because sometimes > I forget to do that, and drain the battery considerably faster. > What is the preffered way to do that? Is ifstated(8) the way? > > istated(8) is monitoring the 'interface link state'. > Is 'no network' recognizable as an interface link state? > What I would like to recognize with ipw0 is what > 'no carrier' would be for an ethernet interface: > is that a good analogy? 'no network' just means > the interface is not associated to any network, > not that there isn't a nework around, right? > > Now I tend to put > > ifconfig ipw0 | grep 'no network' > /dev/null && ifconfig ipw0 down > > into the root's crontab but that seems a bit crude. > > Jan >
Hmm, there used to be sensors on my thinkpad T60, now sysctl hw.sensors shows me nothing, and sysctl hw does seem to wait something, i gave up after an half minute and ^C'd my way out of sysctl. -Artturi
