Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 7 Apr 1999 22:52:44 +0200 (MET DST)
From:      Christoph Weber-Fahr <listmail@helena.callcenter.systemhaus.net>
To:        garyj@muc.de
Cc:        freebsd-isdn@freebsd.org
Subject:   Re: vanishing isdnd - whats that ?
Message-ID:  <199904072052.WAA05193@helena.otelo-call.de>
In-Reply-To: <199904071936.VAA00727@peedub.muc.de> from Gary Jennejohn at "Apr 7, 99 09:36:54 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
Hallo,

> >> you have to set idletime-outgoing to a non-zero value. I use 30, but _any_
> >> value other than 0 is OK. Perhaps the code for I4B_TIMEOUT_UPD should use
> >> a default if a value of 0 is passed in ?
> >
> >Hm... but why does it work then, after beeing started ? Remember,
> >this problem only occurs after recalculation of timeouts.
> 
> the ioctl in the kernel is only called when isdnd notices that it has to
> update the rates value. This isn't likely to happen immediately after
> it's (re)started.

Hm... but it shouldn't it be likely to happen sometime during 
'active duty' - at least when connections are opened ?

I can 
- start isdnd
- open connection
- work with it for a few hours

with these settings just fine. I just should avoid rate zone changes...

Curious...

Regards

Christoph Weber-Fahr



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isdn" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904072052.WAA05193>