[ please keep me in CC since the BTS hasn't affected a maintainer to acpi-support yet ]
Hi Angus, thanks for your bug reports. You appear to have some knowledge on the topic and evidently some interest, would you be interested to co-maintain the package? > suspend.d/55-down-interfaces.sh takes down all interfaces that exist, > even those that are already down and resume.d/62-ifup.sh diligently > brings up all the interfaces that were taken down. This means that my > ethernet interface (which is managed through ifplugd) was correctly > down, but acpi-support tries to bring it up on resume. > > A simpler alternative that would also fix this issue would be > something like: Can you explain me why it would fix the issue? > suspend.d/55-down-interfaces.sh: > ifdown -e lo -a The -e switch of ifdown is undocumented, what does it do? Exclude an interface ? > resume.d/62-ifup.sh: > ifup -a This would start all interfaces marked auto in /etc/network/interfaces and not necessarily only those that were up when we suspended. What do I miss? > If you want to be more persistent and fall through to ifconfig down, > as the current 55-down-interfaces.sh does, you should walk through > `cut -d= -f 1 /etc/network/run/ifstate`, rather than all interfaces > that currently exist. How can a network interface appear in ifconfig if it's not up ? Cheers, -- Raphaël Hertzog -+- http://www.ouaza.com Freexian : des développeurs Debian au service des entreprises http://www.freexian.com
