On Mon, Jun 12, 2000 at 01:28:20PM -0400, [EMAIL PROTECTED] wrote: > When I changed Hz to 120 so I can do 30Hz I get complaints from X-Windows and > Top. Are there any patches for programs that expect Hz to always be 100? > Anything that can't handle 100 and 1024 is usually considered broken. This usually implies that there is a '#define HZ 100' or '#define HZ 1024' somewhere in the code, which you can fix and then recompile it. The problem lies somewhere between current reality and Linus' stated desire that the kernel expresses time values in a timescale that is standard for a particular architecture, i.e., in units of (1/100) sec for i386, (1/1024) sec for alpha, etc., but _NOT_ in terms of (1/HZ). A brief perusal of kernel code will tell you that this is not true, and that if you set HZ=120, you get some code that expresses time in terms of 1/100 sec, and some in 1/120 sec. The procps package (which includes top) guesses the current tick size based on watching interrupts, IIRC. In the interest of not wasting too much time, it is not very accurate, so it may misinterpret 120 as either 100 or 128. dave... -- [rtl] --- To unsubscribe: echo "unsubscribe rtl" | mail [EMAIL PROTECTED] OR echo "unsubscribe rtl <Your_email>" | mail [EMAIL PROTECTED] --- For more information on Real-Time Linux see: http://www.rtlinux.org/rtlinux/
