Tag Info

Hot answers tagged

2

ntpdate is giving you the "socket in use" error because you have a NTP daemon running. This is good. Now, the problem with VMs is that they tend to have a huge time offset (because of being frozen and restarted), and by default NTP panics and exit when the clock skew is too big. Add the following lines to /etc/ntp.conf: tinker panic 0 server ...


2

There's no standard definition for “fully start”. If you come up with a definition, there may or may not be a way to detect it. If your definition of “fully start” is “wait until the application becomes idle, waiting for user input”, then you can trace its system calls and look how long it takes to start reading user input. strace -o myapp.strace -tt myapp ...


2

Look at the ls -l /etc/localtime to see at what time the change happened. Then look through logs such as /var/log/audit/audit.log and /var/log/secure for what might have started at around that time. Note that now systemd has taken over /etc/localtime and there is a command timedatectl set-timezone <zone> that can change this file too. Also, there ...


2

The answer is: You can not! Linux is no real time system. The idea of UNIX and therefore Linux, too, is to provide minimum answer times, while the system is shared between multiple users and system processes. Depending on when you start the command, you might have to wait for a important system process to give you your share of processor time. Further the ...



Only top voted, non community-wiki answers of a minimum length are eligible