Applications caused by Linux leap second problems

Applications caused by Linux leap second problems

Leap second indicates that the Linux system automatically adjusts the system time. This usually happens at the end of a month, probably at the end of June and December, when leap second occurs, the application (Java) may be busy, resulting in slow response.

If leap = 01 is returned in the following command, it means that leap second will occur.

Ntpq-c "lassoc"-c "mrv & 1 & 1 & 999 leap, srcadr, stratum"

If the following command returns "no leap seconds", it indicates that no leap second occurs.

File/etc/localtime

If the following command returns, leap second occurs.

Ntptime | egrep 'ins | DEL'

If your system has the leap second problem, you can solve it in the following ways.

-Stop the ntpd service.

-Reset the Kernel Status and frequency,

Ntptime-s 0-f 0

-Append-x to the/etc/sysconfig/ntpd file to enable slew mode.

-Start the ntpd service.

Leap second occurs in a specific ntpd and kernel. In this article, a C program for leap second stress testing is attached.

This article permanently updates the link address: