On Wed, 2012-09-19 at 18:36 +0200, Per Jessen wrote:
James Knott wrote:
Per Jessen wrote:
Without knowing seamonkey in detail, it's a bit of guesswork, but try capturing the output (strace -o <file> -p
https://docs.google.com/folder/d/0B5LapMwk8iPrZXpDSVlaN3lVekU/edit?docId=0B5... Hmm, doesn't say a lot - SM keeps doing a recvfrom() which keeps returning -EAGAIN. It's a socket fd=4, but I don't see a bind() or connect() anywhere.
Look in /proc/{pid}/fd/{fh#} points and that will tell who where the file handles are bound to [in this case, 4 is the fh#]
That it is using recvfrom() probably means it's UDP. I wonder if it might be name resolution.
That is a good guess, I'd put my money on that. EAGAIN means there was an attempt to read from a socket but nothing was available. I'd install the bind caching nameserver packages, start bind, and point my resolver at 127.0.0.1 - then see if the problem goes away. If it does, that it is a DNS problem or a resolver bug.