On Sat, Oct 20, 2001 at 03:25:26PM -0700,
Derrick MacPherson <derrick@???> is thought to have said:
> I noticed a delay when recieving mail on one server, and not really
> knowing how to figure out what the delay was, I did a quick man -k on
> trace, and saw the command truss. Now I don't know jack about truss, so
> I will put the output here, and maybe someone offlist can tell me if
> there is anything of interest here, and if it looks like a problem
> here... (this is a truss -p pid#)
>
>
> (null)() = 1 (0x1)
> accept(0x0,0xbfbff30c,0xbfbff238) = 1 (0x1)
> dup(0x1) = 2 (0x2)
> fcntl(0x1,0x3,0x0) = 2 (0x2)
> fcntl(0x2,0x3,0x0) = 2 (0x2)
> fork() = 66779 (0x104db)
> close(2) = 0 (0x0)
> close(1) = 0 (0x0)
> wait4(0xffffffff,0xbfbff22c,0x1,0x0) = 0 (0x0)
> SIGNAL 20
> SIGNAL 20
> SIGNAL 20
> select(0x1,0xbfbff240,0x0,0x0,0x0) ERR#4 'Interrupted
> system call'
> sigaction(SIGCHLD,0xbfbfeff4,0xbfbfefdc) = 0 (0x0)
> sigreturn(0xbfbff048) ERR#4 'Interrupted
> system call'
> wait4(0xffffffff,0xbfbff22c,0x1,0x0) = 66779 (0x104db)
> wait4(0xffffffff,0xbfbff22c,0x1,0x0)
This doesn't show anything except that it forked off a child process.
You'd be better of trying to debug this using the built-in debugging
features in exim (using, say, 'exim -d11 -bh <ip of server>' to simulate
a SMTP session with that server). The -d11 will allow you to see the
results of the DNS lookups that occur, in case you're dealing with DNS
time outs, say.
It's probably DNS or your rfc_1413_query_timeout being set too high while
the remote site is blocling identd lookups.
Tabor
--
--------------------------------------------------------------------
Tabor J. Wells twells@???
Fsck It! Just another victim of the ambient morality
