On Sun, 29.09.02 19:07, Nicolas Boullis (nboullis@debian.org) wrote:
> Hi!
>
> How would you compare this to miid
> (http://www.wossname.org.uk/~mathie/software/#miid)?
Hmm, I must admit, there are not that much differences. If I had known
of that piece of software before I'd have improved it, and not written
my own. However, ifplugd has some advantages:
- It makes use of the more reliable (newer) ETHTOOL ioctl()s. miid's
author reports some problems with Apple TiBooks. I'd guess they go
away when using ifplugd. (ifplugd falls back to the old ioctl()s, when
the ETHTOOL ioctl()s fail.)
- It may beep on successful (or failed) interface configuration or
when the plug is pulled/connected
- Has a --ignore-fail mode which makes it compatible with PCMCIA
network drivers, which are not loaded all the time
- The spawned subprogram's stdout/stderr is redirected to syslog
- And most important: it works. miid doesn't. At least on my
machine. First miid did not want to startup because the interface
wasn't up. This is somewhat a paradoxon, I think. After doing
"ifconfig eth0 up" by hand miid simply locked up my machine. After
rebooting I got miid working for 2 minutes, than my machine locked
up again. this simply doesn't occur with ifplugd. The need of
"ifconfig eth0 up" may be caused by some strangeness of the 8193too
driver I am using. However, ifplugd works around this
maybe-bug. miid is unusable on my machine, while ifplugd is.
- Different delays for setting an interface up and down. This is quite
useful, since you mostly want to use networking immediately when you
plug your cable in. Thus you set the up-delay to 0. However, you
may want to unplug the cable for a short time without having the network shut
down. Thus you set the down-delay to 10. (or something like this)
miid doesn't distuinguish between these to times.
I cannot see any disadvantages of ifplugd over miid.
I vote for ifplugd!
Lennart
--
name { Lennart Poettering } mail { lennart@poettering.de }
icq { 11060553 } www { http://www.poettering.de/lennart/ }
loc { hamburg, germany } pgp { 0x1A015CC4 } hack { .phi. }
Attachment:
pgpoXGm_ZeBFx.pgp
Description: PGP signature