On May 31, 2006, at 6:26 PM, Tore André Klock wrote:
Truss output looks like this, which is about the same as before: 0.0010 pollsys(0x00467DC0, 10, 0xFFFFFD7FFFDFFAD0, 0x00000000) = 1 0.0011 pollsys(0xFFFFFD7FFFDFF6B0, 5, 0xFFFFFD7FFFDFF690,
0x00000000) = 0 0.0011 pollsys(0xFFFFFD7FFFDFF6B0, 5, 0xFFFFFD7FFFDFF690,
0x00000000) = 0 0.0011 pollsys(0x00467DC0, 10, 0xFFFFFD7FFFDFFAD0, 0x00000000) = 1 0.0012 pollsys(0xFFFFFD7FFFDFF6B0, 5, 0xFFFFFD7FFFDFF690,
0x00000000) = 0 0.0012 pollsys(0xFFFFFD7FFFDFF6B0, 5, 0xFFFFFD7FFFDFF690,
0x00000000) = 0 0.0012 pollsys(0x00467DC0, 10, 0xFFFFFD7FFFDFFAD0, 0x00000000) = 1
The one strange thing here is that there seem to be two different poll
() calls somewhere doing different things. If this is the case, the
only place where this could happen is in PostgreSQL code. You haven't
configured and enabled that also, right? :)
You mentioned maybe "some connection is talking to Dovecot
constantly". Is there a way I can track down what that might be? I assume you are
talking about a socket, but without knowing what to look for I can't see anything
unusual in the netstat output.
Give -v pollsys parameters to truss. It shows what fd it is that's
returning something all the time. Looks like in the one Solaris
system I have you can get a list of file descriptors by looking at /
proc/pid/fd/ directory contents. But I don't know how you could know
where the sockets are connected to.