Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Diagnose and recover from a coreservicesd hang' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Diagnose and recover from a coreservicesd hang
Authored by: cooperman on Oct 17, '03 01:36:11PM

I havent tried this to fix a coreservicesd problem but the 'normal' way to restart a process is to use the kill command. Heres how:

Firstly find out the process ID of the offending program by using the following command and looking for the pid that corresponds with the dodgy process:

ps -ef

Once you have the pid, issue the following command as root (using sudo if you can):

kill -HUP pid

where pid = the numerical process ID.

This should restart the single process. Hope it helps.



[ Reply to This | # ]
Diagnose and recover from a coreservicesd hang
Authored by: cooperman on Oct 17, '03 01:46:26PM

Sorry, that should have been :

ps -aux

to see the process listing.



[ Reply to This | # ]
Diagnose and recover from a coreservicesd hang
Authored by: stetner on Oct 17, '03 08:20:26PM

Kill does not 'restart' processes, it sends a signal to them, and if they catch the signal they can restart themselves. If they don't catch it (or ignore it), they die. If they have been started by a watchdog type process like init, they may be restarted if they have been configured to restart.

Therefore you need to know what the specific process in question will do when 'killed'.

I have not looked into whether coreservices will restart or not, but I am just pointing out that kill will not, in general, 'restart' processes.



[ Reply to This | # ]