On 2011-10-25, A C <[email protected]> wrote: > On 10/25/2011 02:06, Uwe Klein wrote: >> A C wrote: >>> On 10/24/2011 16:04, Richard B. Gilbert wrote: >>> >>>> >>>> 64MB is not a lot of RAM by today's standards. Can you install more for >>>> testing purposes? >>> >>> >>> Unfortunately not. There are only four slots and I don't have any >>> sticks larger than 16MB so 64 is it for now. However, for the little >>> that the machine does (it's only job is ntpd and gpsd) I think 64 >>> should be adequate. >> Heheh, still got my MVME167 with 8MB of RAM running SysVR3.6. >> >> Are you using the local machine as X-Display? >> >> Can you go down to a nongraphical runstate and >> work via a remote (telnet) session from another box? >> >> If nothing else works kill the wedged process hard >> to create a core dump? > > I am not using local graphics. There is no desktop environment in use > on this machine at all. In fact there is no monitor on the machine (at > least not full time). My Xterm and Xclock are exported to a remote machine.
?? So why are you using X at all? Xterm can surely be replaced by the console. And xclock by running date to tell you what time the machine thinks it is (I assume you use that to check to see if ntpd has stopped controlling the clock) > > I need to wait for the process to stall again. It will take a couple > days for that to happen and then I'll try a kill-9 after trying to run a > stack trace. A SIGTERM kill managed to stop the ntpd process this time > but it never generated core. _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
