On 3/28/06, Oliver Kurth <[EMAIL PROTECTED]> wrote: > severity 352479 important > > On Sun, 2006-03-19 at 11:21 -0600, Eric Evans wrote: > > [ Note: For this bug to be 'grave', it would have to be unusable by > > most or all users, cause data loss, or introduce a security hole. I > > don't think it qualifies on any of these counts and should probably > > be downgraded to 'important', (I'll leave that to Oliver though). ] > > Taking your advice, and downgrade to 'important'. > > I just uploaded a new version (0.28-1), which now should work properly > with udev. Please see if that version closes this bug - I wasn't sure, > so I did not close it yet. > > Greetings, > Oliver > > >
Sorry, this has completely slipped my mind. I could blame the Department for auditing me at work, but that was only last week so I can't blame it legitimately. It just occured to me to check whether this was still open, and saw that it was, which reminded me that I hadn't followed up on it recently. For the past few weeks, I haven't noticed any problems with ifplugd and its operation. Insertion and removal of a Sharp Zaurus now appears to lead to upping and downing of usb0 faultlessly, and ifplugd will also monitor other interfaces without problems, the list now extending to ppp0, eth0, and usb0. As far as I am concerned, this bug is now closed. Feel free to do so, and thank you to Eric for all the work you put in! Ciao, J
