Re: Reviving Gnus after suspend/hibernation

[Ted Zlatanov]

On Thu, 27 Oct 2011 20:14:58 +0200 Eli Zaretskii <address@hidden> wrote: 

>> From: Ted Zlatanov <address@hidden>
>> Date: Thu, 27 Oct 2011 13:41:43 -0400
>> Cc: address@hidden
>> 
>> Asking emacs-devel since the Gnus list didn't have any answers:
>> 
>> On Mon, 24 Oct 2011 09:23:09 -0400 Ted Zlatanov <address@hidden> wrote: 
>> 
TZ> On Tue, 18 Oct 2011 18:39:11 +0200 address@hidden (Ludovic Courtès) wrote: 
LC> When Gnus is left plugged or has non-agentized nnimap groups, recovering
LC> from suspend-to-RAM or hibernation has always been a problem for me:
LC> sometimes Emacs is frozen upon resume, trying to get data from some IMAP
LC> stream.
>> ...
TZ> (Assuming modern GNU/Linux system is the main focus based on your
TZ> commands)
>> 
TZ> Is there a D-BUS signal for this, and can Emacs catch it?  If so I could
TZ> try to close the open connections in that handler.
>> 
TZ> What happens on a W32 system?
>> 
>> Any help is appreciated.  I don't know anything about these system events.

EZ> What exactly is the question?

Sorry, I cut too much context.

Active Emacs network connections are not always closed properly upon
resuming from suspend.  This is a problem with GnuTLS, which keeps
waiting for data and hangs Emacs.  So I want to write a resume handler
that will close all the GnuTLS connections.

On Linux I think this is done with D-BUS, but is there a way on W32 as
well?

Thanks
Ted