-
-
Notifications
You must be signed in to change notification settings - Fork 439
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
STARTTIME is incorrect #202
Comments
Can you check the issue using the current master branch (or the latest release version 3.0.2)? |
I downloaded 3.0.2-1 package from debian testing (bullseye), installed it in Ubuntu 20.04.1 LTS and |
Unfortunately we do not have much influence on when downstream distributions pull newer versions from here. For a list which version is available where have a look at #62 (comment). Also as noted in #62 (comment) you might be able to use the htop snap as an alternative. |
Also note "production requirements" are documents written by people. They can be amended if you care to avoid the small bug enough to warrant that. |
I have several up-to-date instances of Ubuntu 20.04 and one of them consistently shows incorrect STARTTIME. The column often shows the same timestamp for most processes with only a handful of top level exceptions like
/sbin/init
and/lib/systemd/systemd
.In the same instance the old issue of process name not being completely refreshed is back. This is very noticeable with postrgesql processes that change process name according to the command they execute. E.g. when a process changes state from running a
SELECT
toidle
the process name changes fromSELECT
toidleCT
keeping the last 2 characters "CT" ofSELECT
.As a reference
top
when run with-o lstart
produces correct process start timestamp.The text was updated successfully, but these errors were encountered: