Consus
2018-04-08 16:50:33 UTC
Hi,
I have mutt connected to IMAPS server that hangs after waking up from
hibernation. It seems that mutt is stuck on read:
$ strace -fp $(pgrep mutt)
strace: Process 25074 attached
read(3,
$ ls -l /proc/25074/fd
total 0
lrwx------ 1 consus consus 64 Apr 4 09:50 0 -> /dev/pts/1
lrwx------ 1 consus consus 64 Apr 4 09:50 1 -> /dev/pts/1
lrwx------ 1 consus consus 64 Apr 4 09:50 2 -> /dev/pts/1
lrwx------ 1 consus consus 64 Apr 4 09:50 3 -> socket:[79931]
$ lsof | grep 79931
mutt 25074 consus 3u IPv4 79931 0t0 TCP XX.XX.XX.XX:YYYY->imap.fastmail.com:imaps (ESTABLISHED)
Is there a way to prevent this?
I'm running Mutt 1.9.4 (2018-02-28) on Linux 4.15.14-gentoo.
I have mutt connected to IMAPS server that hangs after waking up from
hibernation. It seems that mutt is stuck on read:
$ strace -fp $(pgrep mutt)
strace: Process 25074 attached
read(3,
$ ls -l /proc/25074/fd
total 0
lrwx------ 1 consus consus 64 Apr 4 09:50 0 -> /dev/pts/1
lrwx------ 1 consus consus 64 Apr 4 09:50 1 -> /dev/pts/1
lrwx------ 1 consus consus 64 Apr 4 09:50 2 -> /dev/pts/1
lrwx------ 1 consus consus 64 Apr 4 09:50 3 -> socket:[79931]
$ lsof | grep 79931
mutt 25074 consus 3u IPv4 79931 0t0 TCP XX.XX.XX.XX:YYYY->imap.fastmail.com:imaps (ESTABLISHED)
Is there a way to prevent this?
I'm running Mutt 1.9.4 (2018-02-28) on Linux 4.15.14-gentoo.