On 2/7/2016 3:25 PM, Mahmood Naderan via dtrace-discuss wrote: >>Same as pretty much every Unix/Linux system: >>"kill -STOP" with a list of process ids to stop them. >>"kill -CONT" with a list of process ids to resume them. > > Excuse me... I am not sure about that. 1) prstat shows many java > processes while ps command shows only 2. Also, after the 'kill -STOP', > again the processes are active (shown in the ps output).
They're showing different things. prstat is showing all processes from all users. "ps" by default shows only the current user's processes. Note the PIDs from your message -- 1660, 1666, 1675, and so on for the processes owned by user "hadoop" but 1264 and 1089 for your own processes. The second ps output doesn't actually show whether the processes have stopped. It doesn't show the state at all -- the default output columns are PID, TTY, TIME, and CMD. None of those columns give the state of the processes. See the man pages for ps and prstat. They have a lot of options. "ps -el" might tell you more. Yes, SIGSTOP and SIGCONT will stop and start processes, provided that they're in a stoppable place (i.e., not blocked uninterruptably in the kernel). -- James Carlson 42.703N 71.076W <carls...@workingcode.com> ------------------------------------------- dtrace-discuss Archives: https://www.listbox.com/member/archive/184261/=now RSS Feed: https://www.listbox.com/member/archive/rss/184261/25769126-e243886f Modify Your Subscription: https://www.listbox.com/member/?member_id=25769126&id_secret=25769126-8d47a7b2 Powered by Listbox: http://www.listbox.com
