Re: Diagnosing non-responsive Mac
site_archiver@lists.apple.com Delivered-To: darwin-dev@lists.apple.com Is there any way to diagnose what is causing a Mac to stop responding to network access? I have a Mac that is using MacOS X server 10.4 and it sometimes will quit responding to network request. When using the computer directly loading an application will cause it to bounce for ever on the dock or beach balling after certain operations. I've seen this before when some program on my system is forking new processes out of control/too rapidly. Just a thought. -Steve _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-dev mailing list (Darwin-dev@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-dev/site_archiver%40lists.appl... At 5:29 PM -0500 5/19/08, stephen joseph butler wrote: On Mon, May 19, 2008 at 5:05 PM, Andre-John Mas <ajmas@sympatico.ca> wrote: I think you're dead on -- this used to happen periodically with my dual G4/450 running Tiger server. In my case it was one of the windows sharing daemons running amok -- if you look in the logs you should see messages about the process table being full. I turned off Windows services and havne't had a problem since -- this may or may not be an option for you. You might try leaving a Terminal instance running, but IIRC, with the process table full you might not be able to execute shutdown or kill. I think I had to quit as much as possible and power cycle the machine to get it back. If you have the same problem and have Activity monitor running you can kill enough of them to be able to restart. This email sent to site_archiver@lists.apple.com
participants (1)
-
Steve Sisak