Re: [pm] fix time after suspend-to-*

[Pavel Machek <pavel@suse.cz>]

Hi!

> > Userspace behavior on suspend transitions is still a bit fuzzy at best. I 
> > am beginning to look at userspace requirements, so if anyone wants to send 
> > me suggestions, no matter how trivial or wacky, please feel free (on- or 
> > off-list). 
> 
> Many userspace applications are not prepared for suspension, like
> Evolution. When suspending the machine for a long time, all IMAP
> sessions are broken as their counterpart TCP sockets timeout. While
> resuming, Evolution is unable to handle this condition and simply
> informs the network connection has been dropped.
> 
> What about sending the SIGPWR signal to all userspace processes before
> suspending so applications like Evolution can be improved to handle this
> signal, drop their IMAP connections and then, when resuming, reestablish
> them?

Not sure... We do not want applications to know. Certainly we can't
send a signal; SIGPWR already has some meaning and it would be bad to
override it.
								Pavel
-- 
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]