[ltp] Re: Question on ifplugd and ACPI suspend

[Bob Alexander]

Wolfgang Karall wrote:
> Use ifplugd with a rather short down-delay (option -d) and just wait
> with plugging in the cable in the office until the resume is finished?
> Because ifplugd will then realize the link is down, and if you connect
> the cable a couple of seconds later it'll reconfigure the interface.
> 
> At least that's how I'm using it (in combination with guessnet).
> 
> Regards
> WK

Wolfgang hello.

You are correct.

Modifying my behaviour can solve the problem.

I am only trying to see if technology can help me with my behaviour and 
not the other way around :)

This is what happens now (time expressed in seconds):

T0: ho my god, must run home
T1: slam the lid of my Thinkpad shut while on the port replicator 
(attached to network)
T2-25: put on the jacket, close papers in the drawers, wipe secretary's 
lipstick from my neck
T26: TP has finished suspending to disk, shove it into my backpack
T30: start the car and ruch home
T430: enter home, kiss wife, wipe her lipstick so the secretary does not 
see it tomorrow, kiss kids
T450: shove my thinpad on my home port replicator, turn everything on 
with my big red switch (powers ADSL routers, thus network and PC)
T470: TP is ready and I begin working again

Given this habit it is difficult that I might remember unconnecting the 
TP and wait for ifplugd to declare the network dead before suspending.

I'd rather give a manual ifup eth0 then :)

What I am looking is a way for ifplugd to issue an ifup whenever it 
starts up even if it senses a link up ... in this way the ifplugd start 
and ifplugd stop capabilities of the swsusp2 script should do what I want.

Thank you,
Bob