Hi all,
I can reproduce the problem and tried looking with strace into it.
The relevant lines of the trace seem to be these:
[pid 18269] socket(PF_FILE, SOCK_STREAM, 0) = 5
[pid 18269] connect(5, {sa_family=AF_FILE, path=@"/tmp/fam-luckas-"},
110) = ? ERESTARTSYS (To be restarted)
[pid 18269] --- SIGALRM (Alarm clock) @ 0 (0) ---
Looks like gam_server is not accepting the connection and courier not
handling that issue well.
At leat for the courier part, this information might help the developer
to fix the issue.
Why gam_server stops accepting connections is another issue to be
researched seperately.
Thanks to http://www.noah.org/wiki/Courier_IMAP_and_FAM I also did a
"netstat -np|grep /tmp/fam-" which showed quite a few connections in the
CONNECTING state. But I guess this is expected given the above strace :-)
Hope this helps resolving the issue.
Regrds,
Uli
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
