Thanks, pushed only the #include change.

ntserv/alarm.c uses setitimer(2) syscall, so if you demonstrate it
doesn't work, raise a bug against the libc or kernel you're using.

Also check that your kernel was not busy synchronising to an NTP
server, as that will change real time intervals.

You might also try adding an RTC and see if that changes it.  ;-)

On Fri, Nov 09, 2018 at 04:08:07AM +0000, Thomas E. Lackey wrote:
> I just built master on my Pi3 on Raspbian, mostly without incident (had to add
> an include for sys/types.h to robot.h).
> 
> However, everything moves at warp speed (pardon the pun).  At first glance, I
> would have estimated the pace at about double.
> 
> I adjusted REALITY in `etc/sysdef` (mistakenly called DISTORTION, which is what
> it is called elsewhere in the code) and found ‘8’ to look about right (the
> default is ‘10’).
> 
> I just built on this Pi this evening, so I haven’t had a chance to dig into the
> code.  My wild guess without looking would be that CPU freq scaling was messing
> with the tick rate or some such strangeness along those lines.
> 
> Anyone with better knowledge of how “reality” is calculated have thoughts on
> what this might be?
> 
> --
> 
> Thomas E Lackey
> 
> diff --git a/robotd/robot.h b/robotd/robot.h
> 
> index 4883e70..8aeecd0 100644
> 
> --- a/robotd/robot.h
> 
> +++ b/robotd/robot.h
> 
> @@ -1,3 +1,7 @@
> 
> +#ifndef __INCLUDED_robot_h__
> 
> +#define __INCLUDED_robot_h__
> 
> +
> 
> +#include <sys/types.h>
> 
> #define PASS           "t"
> 
> #define PASS2          "tover"
> 
> @@ -433,3 +437,5 @@ extern int  Xplhit;
> 
> #define TR_DEFEND              7
> 
> #define TR_OGG                 8
> 
> #define TR_TORP                        9
> 
> +
> 
> +#endif /* __INCLUDED_robot_h__ */
> 

> _______________________________________________
> netrek-dev mailing list
> netrek-dev at us.netrek.org
> http://mailman.us.netrek.org/mailman/listinfo/netrek-dev


-- 
James Cameron
http://quozl.netrek.org/