Return to BSD News archive
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!yarrina.connect.com.au!werple.apana.org.au!otis.apana.org.au!serval.net.wsu.edu!netnews.nwnet.net!oracle.pnl.gov!osi-east2.es.net!lll-winken.llnl.gov!unixhub!news.Stanford.EDU!yergeau From: yergeau@leland.Stanford.EDU (Dan Yergeau) Newsgroups: comp.os.386bsd.development Subject: Re: emacs (19.28) and freebsd (1.1) problems Date: 28 Nov 1994 18:48:59 GMT Organization: Stanford University, CA 94305, USA Lines: 33 Message-ID: <3bd8mr$35i@nntp.Stanford.EDU> References: <JZOUB0WC@math.fu-berlin.de> NNTP-Posting-Host: adelbert11.stanford.edu In article <JZOUB0WC@math.fu-berlin.de>, Thomas Graichen <graichen@omega.physik.fu-berlin.de> wrote: >hello > >yesterday i build emacs 19.28 on freebsd 1.1 and found two problems: > >- if i start emacs - the system reads the binary from disk (that i can >listen to) and then it waits ~ 5 seconds (top: emacs is sleeping and the >system is 98 % idle at that time) - can anybody tell me where this is coming >from (it's a 386/387DX40) - is it from dynamic linking (because there are ~ >8 shared libraries to load) - but if so i think the system should'nt be idle >and it is totally reproducable (the next emacs - the same thing) It may be due to an inability of resolve your network host information (via gethostbyname()?). Newer versions of emacs are very persistent about trying to get this information (10 trials with a one second sleep after each failure). If your hostname isn't aready in /etc/hosts, put it there, even if you aren't on a network. -- Dan Yergeau You are in a twisty little passage yergeau@gloworm.Stanford.EDU of standards, all conflicting. #include <std.disclaimer> -- -- Dan Yergeau You are in a twisty little passage yergeau@gloworm.Stanford.EDU of standards, all conflicting. #include <std.disclaimer>