Re: Delay in connecting to service
On Fri, Oct 06, 2000 at 11:16:00AM +0200, Fredrik Liljegren wrote:
> Marcin Owsiany <porridge@pandora.info.bielsko.pl> writes:
> > On Fri, Oct 06, 2000 at 09:56:44AM +0200, Fredrik Liljegren wrote:
> > > Oct 2 08:52:04 bifrost sshd[228]: debug: Forked child 18444.
> > > Oct 2 08:53:19 bifrost sshd[18444]: Connection from 10.10.11.5 port 2038
>
> > sshd is waiting for DNS lookup timeout
>
> I don't think so, because that is another delay that we've had earlier
> but dont have anymore, like the following:
>
> Aug 24 17:16:54 bifrost sshd[478]: Accepted rsa for tombe from 10.10.12.5 port 2310
> Aug 24 17:17:09 bifrost sshd[478]: Could not reverse map address 10.10.12.5.
>
> This comes after the authentication has started, not as the above,
> between the fork and the connection to the new child.
>
> Is there any other DNS-lookup that is done before the child is
> connected to the port, that can explain the delay I get when I start
> it from inetd also?
Yes, in TCP wrappers (tcpd or libwrap). AFAIK sshd is linked with libwrap.
> > BTW: This is probably not best place to ask such questions. Use
> > debian-isp instead...
>
> Because they would know more?
No, just because debian-devel is a list for discussions on developement of
Debian.
regards
Marcin
--
+--------------------------------+ The reason we come up with new versions
|Marcin Owsiany | is not to fix bugs. It's the stupidest
|porridge@pandora.info.bielsko.pl| reason to buy a new version
+--------------------------------+ I ever heard. - Bill Gates
Reply to: