Jan dixit (2011-01-20, 02:33): > On Thu, 20 Jan 2011 02:28:22 +0100, Antoni Grzymala <ant...@chopin.edu.pl> > wrote: > > Jan dixit (2011-01-20, 02:26): > > > >> On Wed, 19 Jan 2011 20:22:51 -0500, Kurt H Maier <karmaf...@gmail.com> > >> wrote: > >> > On Wed, Jan 19, 2011 at 8:15 PM, Jan <k...@unstable.nl> wrote: > >> >> Maybe surveilling /var/log/messages (lines are similar to dmesg > >> >> output) > >> >> for lines that include "eth0" and "link" might work. > >> > > >> > wpa_supplicant puts all its info (i.e., CTRL_EVENT_DISCONNECTED) out > >> > on stderr. Could just pipe that to a shell script. > >> > >> Does wpa_supplicant work with wired devices? > > > > As a 802.11x supplicant? AFAIR yes. > > I thought the intention was to see if there is a cable plugged in, and I > believe there are better ways for this task than having a wpa_supplicant > running, this seems overpowered.
For that you could use netplug or ifplugd (and others) or even write a script that watches carrier on an interface, certainly though the former options make more sense as someone took the trouble to write it in C (probably). -- [a]
