On 11/14/11 16:50, David Woolley wrote: > Phil Stracchino wrote: > >> lock up the system. I can sometimes, not always, get it to stop >> properly by sending it a SIGKILL instead of SIGTERM. > > If SIGKILL doesn't work you have a kernel or hardware problem, not a > problem in ntpd.
Oh, I'm quite sure it's hardware *related*, since the problem occurs only when trying to stop ntpd and only when ntpd is using the USB-connected GPS sensor as a hardware reference clock. I was hoping someone else might have encountered this or a similar problem before and know how to fix, avoid, or work around it (other than by not using the GPS refclock). -- Phil Stracchino Babylon Communications [email protected] [email protected] Landline: 603.293.8485 _______________________________________________ questions mailing list [email protected] http://lists.ntp.org/listinfo/questions
