On 2025-02-17 01:32:14 +0100, Chris Hofstaedtler wrote: > * Vincent Lefevre <vinc...@vinc17.net> [250217 01:20]: > > On 2025-02-17 00:33:59 +0100, Chris Hofstaedtler wrote: > > > * Vincent Lefevre <vinc...@vinc17.net> [250217 00:28]: > > > > On 2025-02-16 23:56:43 +0100, Chris Hofstaedtler wrote: > > > > > % w > > > > > 23:53:23 up 1 min, 2 users, load average: 0.06, 0.03, 0.00 > > > > > USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT > > > > > ch 192.168.64.1 23:53 1:24 0.00s 0.02s > > > > > sshd-session: ch [priv] > > > > > ch - 23:53 1:24 0.00s 0.04s > > > > > /usr/lib/systemd/systemd --user > > > > > > > > No data for xterm. Other terminals are affected too, such as > > > > GNOME Terminal. > > > > > > AFAIK this is expected. You should have a single entry for the X > > > session, if you started it from a session manager. > > > > This means that it is no longer possible to get information that > > could be obtained previously: IDLE, JCPU, PCPU, WHAT associated > > with the terminal. Unless there is another tool to get such > > useful information, this is a regression. > > Please ask upstream. Would be good if these things work. > Although personally I've only ever cared about the IDLE column.
There are various uses, in particular together with the terminal name (TTY), when it works. However, I prefer to use my own "idle" script, which sorts the terminals by idle time. So I can see what I used recently. I can even raise the terminal window with "wmctrl -R <tty>". -- Vincent Lefèvre <vinc...@vinc17.net> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
