Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!ohstpy!miavx1!pemurray
From: pemurray@miavx1.acs.muohio.edu (Peter Murray)
Newsgroups: comp.unix.ultrix
Subject: Re: _SLOW_ response to login request
Message-ID: <2478.27090a9e@miavx1.acs.muohio.edu>
Date: 3 Oct 90 02:46:05 GMT
References: <1990Sep17.203920.26835@ux1.cso.uiuc.edu>
Distribution: comp.unix.ultrix,comp.sys.dec
Lines: 22

In article <1990Sep17.203920.26835@ux1.cso.uiuc.edu>, hudson@ux1.cso.uiuc.edu (John Hudson) writes:
> I had read in several previous postings of unusually long waits for
> logins under Ultrix and had only seen one solution - use a non-DEC
> version of bind.
> 
> I am running Ultrix 3.1 (UWS 2.1) on a VaxStation II-GPX.  Typical waits
> for valid logins are from 90-120 seconds, sometimes longer.  The problem
> seems to be independent of machine load, request location (local, remote,
> or console) and communication program (rlogin, telnet, etc.).  

Are you running the Gateway version of telnetd (telnetd.gw)?  This version
of the daemon allows users to use the login: prompt to connect to other
machines on decnet and the internet.  When you mentioned that you replaced
bind, my ears perked up.

Running the non-gateway version of telnetd might increase response time.

Peter
-- 
Peter Murray            Neat UNIX Stunts #6:             pemurray@miavx1.bitnet
176 Thompson Hall         csh> ar m God           pmurray@apsvax.aps.muohio.edu
Oxford, OH 45056                       NeXT Mail:  pmurray@next4.acs.muohio.edu