Date: Sun, 02 Feb 1997 09:14:59 +0000 From: Meir Dukhan <mdukhan@bis.co.il> To: Greg Lehey <grog@lemis.de> Cc: questions@FreeBSD.org Subject: Re: Enabling KTRACE option Message-ID: <32F45B13.41C67EA6@bis.co.il> References: <199702011048.LAA28345@freebie.lemis.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Thanks Greg, I think you get it ;) Greg Lehey wrote: > > Meir Dukhan writes: > > Hi, > > > > I built a new kernel (2.1.6) with options KTRACE enabled, because I > > wanted to be able to trace some processes. > > > > But now, it take a long time (120-150 seconds) to reboot, and sometimes > > telnet'ing it from a another machine in our net, don't work. > > > > What could be the cause of this ? > > Not KTRACE, anyway. > > > If I want to reboot and load my precedent kernel, is all I have to do is > > to give /kernel.old at boot prompt ? (I can't try now, because ppl here > > need mail and telnet). > > Check the names you have in /. Anything startin with /kernel should > be bootable. > > As to the other problem: is the boot just slow from start to finish, > or does it hang at some point? If so, where? I frequently see It is just slow and doesn't hang. > problems like this with DNS queries. Are you running named? You get it! I'm running named. Do I have to understand that it is a known problem ? BTW, it seems that the impossibility to telnet is just within the 3-5 minutes after the boot, and after that telnet work fine. Is this related to named too ? Tia -- Meir
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?32F45B13.41C67EA6>