Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!decwrl!nic.hookup.net!swrinde!cs.utexas.edu!news.unt.edu!ponder.csci.unt.edu!jackson From: jackson@ponder.csci.unt.edu (Bruce Jackson) Newsgroups: comp.os.386bsd.bugs Subject: Re: CPU hungry routed Date: 26 Jan 1994 03:28:43 GMT Organization: University of North Texas, Denton Lines: 33 Message-ID: <2i4o1b$e4b@hermes.unt.edu> References: <9401251722.AA26534@puffin.usmcs.maine.edu> NNTP-Posting-Host: ponder.csci.unt.edu In article <9401251722.AA26534@puffin.usmcs.maine.edu>, George P. Swanton <swanton@puffin.usmcs.maine.edu> wrote: >I noticed that a program I'm working on ran about twice as fast on my >laptop as on my desktop, both 486/33, so I looked for hogs: >USER PID %CPU %MEM VSZ RSS TT STAT STARTED TIME COMMAND >root 64 98.8 0.9 172 136 ?? Rs Fri07PM 5279:57.06 routed -q >Could someone suggest what routed might want with 98.8% of the cpu and what >might cause such behavior? I don't know why routed is using so much cpu time. However, do you really need to run routed? Most people can get away with static or combination routing. Routed is only needed when you are connected to a network that changes topology. Since most networks are static you can insert the needed routes into the routing table with the route command. If your local network is static but is connected to a dynamic network you should use combination routing where your default route is to the router that handles the dynamic route outside of your local network. The most likely fix to your problem is to not run routed and add the needed routes with route. You can list the routes in your routing table with "netstat -r" If all of your routes are the same machine than you should be using that machine as your default instead of running routed. -- Bruce Jackson | Univ. of North Texas | jackson@cs.unt.edu UNIX Systems Admin. | P. O. Box 13886 | GAB 550E (817)565-2279 Dept. of Computer Sci.| Denton, Tx. 76203-3886 | FAX: (817)565-2799