One quick solution would be to write your own finger client for
Radiator to run. It could do things like:
use a shorter timeout
remember the state of the line from previous calls
etc.
On Fri, 11 Jun 1999, Stephen Roderick wrote:
> On Fri, 11 Jun 1999, Mike McCauley wrote:
>
> > Hello Ferhat.
> >
> > What NasType are you using, and what does your finger say when it times out?
> > Try running it by hand, to see.
> >
> > With that information, we might be able add a patch that will detect a timeout
> > and not delete the user.
>
> The BIG problem isn't deleting the user, it is the HUGE delay that occurs
> while Radiator is trying to verify the user. This stops all other
> authentications, and when you are running a lot of ports it is disastrous.
>
> Steve
>
> ---
> Steve Roderick ProAxis Communications, Inc.
> [EMAIL PROTECTED] Internet Access Provider
> (541) 757-0248
>
>
> ===
> Archive at http://www.thesite.com.au/~radiator/
> To unsubscribe, email '[EMAIL PROTECTED]' with
> 'unsubscribe radiator' in the body of the message.
>
>
Jim
[EMAIL PROTECTED]
===
Archive at http://www.thesite.com.au/~radiator/
To unsubscribe, email '[EMAIL PROTECTED]' with
'unsubscribe radiator' in the body of the message.
