χ Wed, 14.08.2002, Χ 09:34, Mike Makonnen ΞΑΠΙΣΑΜ:
> On Tue, 13 Aug 2002 20:36:39 +0400
> "Vladimir B. Grebenschikov" <[EMAIL PROTECTED]> wrote:
> > > Yes, there is a simple solution: adjust the timeout in dhclient.conf.
> > It is not solution - it is workaround
> > - I do not wand any dhcp activity if I have no media (say in car)
> > And dhclient in case of failure of detecting network address will
> > install lask seen one, with last seen default gateway and I will get
> > very long timeout while any of my apps will try to reach network
> > instead of instant 'no route to host'
> Then, bring the interface down manually (it's even easier now that
> you can insert your own script in the rc boot process). I am not being
Of course I can patch my rc.d/network1 manually or/and add number of
"smart" scripts, but I simply wants to share solution with other people.
> Your suggestion, while it solves your problem, would create a problem
> for others (re-read the quote).
Why it will create problems for others ? You need explicitly ask for
if you will use old-style:
nothing will changed in dhcp behavior
My personal opinion - best choice add key to dhclient - which do not
ever try to send requests or record leases in case of no carrier on
media and do not stop boot process in this case.
Some times ago I have patch dhclient for this, but I am not satisfied
with the patch, so do not send it to anybody.
> Mike Makonnen
Vladimir B. Grebenschikov
[EMAIL PROTECTED], SWsoft, Inc.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message