aboutsummaryrefslogtreecommitdiffstats
path: root/meta-oe/recipes-graphics/numlockx
diff options
context:
space:
mode:
authorAndreas Müller <schnitzeltony@googlemail.com>2013-09-16 09:06:35 +0200
committerJoe MacDonald <joe@deserted.net>2013-09-16 10:23:25 -0400
commit080887cf4a95455d11e7a3e176c7c35740e72ea6 (patch)
tree2754f294dcb18da34c3b42508f8825aed0fe3809 /meta-oe/recipes-graphics/numlockx
parent4ddfb3e92fdcffccfcbae1b4003a5d7c3385a637 (diff)
downloadmeta-openembedded-contrib-080887cf4a95455d11e7a3e176c7c35740e72ea6.tar.gz
ntp: disable automatic panic shutdown for ntpd
Taken from [1]: "However, if the difference between the client time and server time is greater than the panic threshold, which defaults to 1000 s, the daemon will send a message to the system log and shut down without setting the clock." On RTC-less or 'fresh' systems with unpredicatble inital date ntpd will stop with work undone (note: I did NOT find the message mentioned above - so it took long way to fix). This is a wide use case for using NTP in production: No need for initial datetime setup by some operator. [1] http://doc.ntp.org/4.1.1/debug.htm Signed-off-by: Andreas Müller <schnitzeltony@googlemail.com> Signed-off-by: Joe MacDonald <joe@deserted.net>
Diffstat (limited to 'meta-oe/recipes-graphics/numlockx')
0 files changed, 0 insertions, 0 deletions