Summary: | net-misc/ntp-4.2.8_p6 segfault on startup | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robin Johnson <robbat2> |
Component: | Current packages | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | RESOLVED TEST-REQUEST | ||
Severity: | normal | CC: | infra-bugs |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robin Johnson
2016-02-15 19:28:19 UTC
you're using old gcc/glibc there, and it looks like a canceled pthreads codepath, so you should really update those also on the topic, i assume you're only using ntp to keep the local server in sync rather than host the time for other servers. why not convert to tlsdate ? it's way simpler to set up, and it has seccomp support. (In reply to SpanKY from comment #1) > you're using old gcc/glibc there, and it looks like a canceled pthreads > codepath, so you should really update those infra stays on stable things for a long time; I've told one of the boxes to upgrade to gcc-4.9.3/glibc-2.21 and we'll see what happens after that. Surprised that NOT updating gcc/glibc should have broken ntpd however. > also on the topic, i assume you're only using ntp to keep the local server > in sync rather than host the time for other servers. why not convert to > tlsdate ? it's way simpler to set up, and it has seccomp support. tlsdate doesn't have any monitoring/mitigation of local clock skew/rate-errors. Some of the host clocks are pretty bad without it (eg: turn off ntpd, and have a variable wrongness of 10 seconds/day). (In reply to Robin Johnson from comment #2) well let us know if it fails w/current stable glibc/gcc. we don't really support older. |