Hi,
I've seen this myself, once or twice. If you search the web for
com.apple.IconServicesAgent you will find plenty of reports. For instance
http://kieranhealy.org/blog/archives/2014/01/07/an-issue-in-mavericks-with-com-dot-apple-dot-iconservicesagent/
It is seemingly more a glitch in OSX 10.9 w.r.t. temporary folders, than
anything to do with macports, although macports for some reason seems
prone to triggering it.
In my case I just removed (using sudo) the temporary directories that
where causing the problem (use Console to find out what those are for
you), rebooted the system and it went away. Haven't seen it come back
for a while now.
Chris
On 05/03/14 15:45, Eric Gallager wrote:
What system are you running on? I do not have that daemon on my
system... Anyway, to deal with unkillable daemons, you usually have to
mess with launchd via launchctl, but I am not sure how you would do that
for the macports user, seeing as it is a "no login" user as you mentioned...
On Wed, Mar 5, 2014 at 9:49 AM, Ghyslain Leclerc <[email protected]
<mailto:[email protected]>> wrote:
Hello.
Sorry if this is a known problem. Been Googling for hours now and
searching the archive up to 6-7 months back to no avail.
I would like to know if someone else has a problem with Macports and
the IconServicesAgent process.
I have a com.apple.IconServicesAgent process running as the macports
user (confirmed via Activity Monitor) which takes 100% CPU for one
of my core (almost, confirmed via Activity Monitor and the ps
command on the terminal) and which I cannot kill. Actually, I
cannot force quit it in activity monitor, but I can kill it with the
kill command in Terminal, but it comes back right away.
I have looked everywhere for a solution. I have found that creating
a temporary folder where the service can work solved to problem for
regular users, but I don’t know how to find the temporary folder for
a “no login” user like macports. Anyhow, I might be saying stupid
things. My apologies if it’s the case. Not an expert in computers.
Anyhow, if someone could let me know if it’s a known problem and if
there is a solution or if I should just accept that my machine now
as one less core.
Thanks
Ghyslain
P.S. : Sorry for my English. Not my first language.
_______________________________________________
macports-users mailing list
[email protected]
<mailto:[email protected]>
https://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
_______________________________________________
macports-users mailing list
[email protected]
https://lists.macosforge.org/mailman/listinfo/macports-users
