This has finally driven me bananas enough to get involved and perhaps try to implement some of this...
On Sun, Jun 18, 2006 at 10:44:23PM +0100, Angus Lees wrote: > On 6/16/06, Raphael Hertzog <[EMAIL PROTECTED]> wrote: > >> ifdown -e lo -a > > > >The -e switch of ifdown is undocumented, what does it do? > >Exclude an interface ? > > Ah. it appears it was deprecated in ifupdown 0.6.5. Shows > how long its been since I updated my suspend script. Yes > it excludes an interface, but we can skip that and just do > ifdown -a without much extra cost. I'd suggest special-casing the ifupdown of lo, and just leave it up throughout the suspend. I'm finding that one of the other ifups generated by the resume script is blocking and the "ifup lo" isn't being executed. This prevents local mail delivery and it is non-trivial to figure out why (if you forget, which I tend to). > Take down / bring up interfaces that the user has tagged > as 'allow-suspend' in /etc/network/interfaces This I quite like, it would certainly stop the suspend script from downing and upping my network-manager-managed eth1, but I'm not sure if it is the right solution; after all, saying "allow-suspend" still doesn't necessarily mean "allow acpi-support to suspend, everything else to ignore". -- Jon Dowland
signature.asc
Description: Digital signature
