site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com How can this work? Once the system freezes, no more commands will execute. Will "exec" make a difference, or why do you think this command will work nonetheless? -- Terry _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... On Mar 30, 2009, at 9:34 PM, Michael Smith wrote: On Mar 30, 2009, at 1:34 PM, Thomas Tempelmann wrote: On Mon, Mar 30, 2009 at 21:24, Terry Lambert <tlambert@apple.com> wrote: If you have Terminal set to not close on exit, and you have a terminal open you can type: exec ps gaxlwww You don't necessarily need to wait until it freezes; depending on how the leak is occurring, you may see it building up well beforehand. Alternately, he can ssh in before the problem has occurred and type sh a bunch of times, and he gets one command per sh instance until he pops the last one off the stack and the ssh session closes. Of course there's that many fewer processes available before the problem occurs, but you really only need two of them: one to find the bad parent, and one to kill it. This email sent to site_archiver@lists.apple.com