lets assume i started htop (or whatever other process) a few minutes ago, so the STARTTIME column shows 17:00. for other processes which started more than 24 hours ago only the date like Jul26 is shown.
so far so good, but if i leave htop running e.g. in a tmux session, then also more than 24 hours or even days later the STARTTIME column still shows 17:00 instead of Jul27 for htop!
at long-time monitoring this can really be misleading (see #595) or even cause mistakes/problems. also the workaround to restart htop is a little bit clumsy and not really applicable if you are monitoring more than a hand full of processes.
either the STARTTIME column of each process must be refreshed at least 24 hours after it has been started
or the complete column for all processes must be refreshed at 00:00 and changed to the past day (if the values are not already a date) - (this would slightly change the current behaviour) -
or refresh STARTTIME regularly like other columns.
alternatively ditch the whole column and replace it with something like "RUNTIME" like proposed in #187, which would be even more accurate.
lets assume i started
htop(or whatever other process) a few minutes ago, so the STARTTIME column shows17:00. for other processes which started more than 24 hours ago only the date likeJul26is shown. so far so good, but if i leavehtoprunning e.g. in a tmux session, then also more than 24 hours or even days later the STARTTIME column still shows17:00instead ofJul27forhtop!at long-time monitoring this can really be misleading (see #595) or even cause mistakes/problems. also the workaround to restart
htopis a little bit clumsy and not really applicable if you are monitoring more than a hand full of processes.alternatively ditch the whole column and replace it with something like "RUNTIME" like proposed in #187, which would be even more accurate.