On Wed, 14 Jun 2017 23:39:00 -0400 Robert Moskowitz <rgm@xxxxxxxxxxxxxxx> wrote: > I found three listed: > > 0 1000 19985 1 20 0 49204 1144 unix_s Sl ? 0:00 > /usr/lib64/libreoffice/program/oosplash --calc > file:///home/rgm/data/excel/htt/expenses-2016.xls > 0 1000 20012 1 20 0 49204 1132 unix_s Sl ? 0:00 > /usr/lib64/libreoffice/program/oosplash --calc > file:///home/rgm/data/excel/htt/expenses-2016.xls > 0 1000 20024 1 20 0 49204 1124 unix_s Sl ? 0:00 > /usr/lib64/libreoffice/program/oosplash --calc > file:///home/rgm/data/excel/htt/expenses-2016.xls > > killed those, but still see the windows. Two things. This display doesn't show the parent process ID for the PID. It might be that the parent of these threads is what is displaying the windows as it waits for their output to update them. Use this command to look for the PPID, and kill it as well (if it isn't 1, :-) ) ps -eF --headers | grep [user name] It won't show the process status, like the earlier command, where we knew that they were sleeping threads. Another possibility is that the windows are artifacts at this point. When you killed the process, it didn't clean up after itself, and left the windows. What happens if you log your user out of X, and then log back in? _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
