Recently I have been getting emacs sessions locking up on my ubuntu machine. With several emacs sessions open, and no way out other than killing the specific session, you need to find the correct PID. But which session is which?<\/p>\n\n\n\n
You can get additional info regarding processes using ps. The example below gives information relating to my currently running emacs sessions.<\/p>\n\n\n\n
$ ps ax | grep emacs\n20284 pts\/7 Sl 1:21 emacs Matrix.txt\n30261 tty2 Sl+ 2:24 \/usr\/bin\/emacs25\n30674 ? Sl 0:00 \/usr\/bin\/emacs25 \/usr\/include\/linux\/errno.h\n30713 pts\/7 S+ 0:00 grep emacs<\/pre>\n\n\n\nThe numbers at the head of the last four lines correspond to the PID for each emacs session. If you need to know the process owner call ps with the argument ‘aux’.<\/p>\n\n\n\n
a - show processes for all users\nu - display the process owner\nx - show processes not attached to a terminal<\/pre>\n\n\n\nThe status flags can be interpreted as follows:<\/p>\n\n\n\n
D - uninterruptible sleep (usually IO)\nR - running or runnable (on run queue)\nS - interruptible sleep (waiting for an event to complete)\nT - stopped by job control signal\nt - stopped by debugger during the tracing\nW - paging (not valid since the 2.6.xx kernel)\nX - dead (should never be seen)\nZ - defunct (\"zombie\") process, terminated but not reaped by its parent<\/code><\/pre>\n\n\n\nIn my case the stalled session was newly opened, so the time was an indication, as was the command line used to start the session. Also, the session was not started from the command line, so without the ‘x’ argument the session did not appear.<\/p>\n","protected":false},"excerpt":{"rendered":"
Recently I have been getting emacs sessions locking up on my ubuntu machine. With several emacs sessions open, and no way out other than killing the specific session, you need to find the correct PID. But which session is which? You can get additional info regarding processes using ps. The example below gives information relating … <\/p>\n