Re: Reviving Gnus after suspend/hibernation

[joakim@verona.se]

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Thu, 27 Oct 2011 20:14:58 +0200 Eli Zaretskii <eliz@gnu.org> wrote: 
>
>>> From: Ted Zlatanov <tzz@lifelogs.com>
>>> Date: Thu, 27 Oct 2011 13:41:43 -0400
>>> Cc: ding@gnus.org
>>> 
>>> Asking emacs-devel since the Gnus list didn't have any answers:
>>> 
>>> On Mon, 24 Oct 2011 09:23:09 -0400 Ted Zlatanov <tzz@lifelogs.com> wrote: 
>>> 
> TZ> On Tue, 18 Oct 2011 18:39:11 +0200 ludo@gnu.org (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?

For the record I have had this or a similar problem since
forever. (there are bugreports etc.) It doesn't have to be a TLS
connection either.

normally I close the gnus connections manually after resume or network
change. When I forget and Emacs hangs, I use this little script:

,----
| #/bin/sh
| `lsof -n|grep emacs|grep nntp|sed "s/.*TCP\ \\([^:]*\\):.*->\\([^:].*\\):.*/  export a=\\1 export b=\\2/"`
| echo $a $b
| ifconfig lo:1 $a
| ifconfig lo:2 $b
| echo press enter when emacs is alive
| read
| ifconfig lo:1 down
| ifconfig lo:2 down
`----

but I don't know what the equivalent is on windoze.

It would be cool if this could be solved properly. (maybe you are seeing
another problem but it does sound similar)


>
> Thanks
> Ted
>

-- 
Joakim Verona