On Wed, Nov 10, 2010 at 3:14 AM, Thiago Macieira <[email protected]> wrote: > On Wednesday, 10 de November de 2010 09:04:02 Dawit A wrote: >> I cannot figure out when the reply was sent back because there is a >> lot of chatter on the system dbus, but I definitely see the pause >> after the following message was sent >> >> 1289374216.174405 sendmsg(23, {msg_name(0)=NULL, >> msg_iov(2)=[{"l\2\1\1I\32\0\0\305\261\5\0-\0\0\0\6\1s\0\5\0\0\0:1.61\0\0\0\ >> 5\1u\0\32\0\0\0\10\1g\0\1s\0\0\7\1s\0\4\0\0\0:1.7\0\0\0\0", > > This is not the one where the delay was expected to happen. This is a reply > message (note the \2 as the second item after the l [little-endian] marker). > And since this is a sendmsg, it means the bus was relaying the reply back to
*sigh* I got everthing crossed up! Indeed since this is the system bus a sendmsg here is response back to the client. For some reason this response does not seem to make it to the client or at least cause the client to react until 25 secs later. Now it is even more weird... > That is actually showing that the target replied immediately. hmm... should I then trace the client and see what it is waiting on ?
