IconServiceAgent

Wed Mar 5 13:00:08 PST 2014

Hi again,

I use a non administrator user for day to day things, so I could not see the main system log.  That was the reason I did not find it when I went looking the first time.  Knowing what to look for, I realized I did not have the admin rights.  Sorry.

Went into Console, found the problematic temp directory, removed it.  Rebooted and no sign of the problem so far (after 10 minutes).  I have not updated Macports, so I wouldn’t say everything is OK yet, but at least, now, the IconSerivcesAgent is not restarting as soon as I reboot the computer.  So progress and I am very much happy.

Thought I would write it here so that if someone else is looking for the info, they know what happened to me.

Thanks for your advice and most importantly your precious time (sure you’re just as busy if not more than me).  Very much appreciated.

Ghyslain

On Mar 5, 2014, at 13:10, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:

> Hi,
> 
>> On 5 Mar 2014, at 05:56 pm, Ghyslain Leclerc <ghleclerc at gmail.com> wrote:
>> 
>> 
>> Hello.
>> 
>> Thank you to you both for your comments.
>> 
>> Eric : I am running on OSX 10.9.2.   I don’t know what to answer about the deamons.  I have not done anything with that.
>> 
>> Chris : I have seen this post.  Thus my comment about the temporary folders.  I have rebooted without deleting any folder and it changes nothing.  I must, I’m afraid, admit I have never worked much with the Console application.  I know it’s for viewing logs, but I can’t navigate it very well.  I will try, but if you could spare a few moments more to nudge me in the right direction, it would be appreciated.  I would be happy to try and delete or create the appropriate folders.
> 
> Start the console application, and just take a look at the main system log "all entries". Search for any entries relating to this and they will tell you the paths that need removing. If you are unsure post here.
> 
>> 
>> I had gathered as well that it was a OSX problem more than a Macports one, but did not know where to get help.   Don’t know if it makes any sense, but the first time I ran into the problem (OSX version 10.9.1), the IconServicesAgent would launch after a selfupdate.  I think it might be because after the rsync, OSX wants to update the icon for every file in the tree.   I might make no sense at all.  Just a thought.
>> 
>> Anyhow, thanks again to you both.
>> 
>> Ghyslain
>> 
>> 
>> 
>>> On Mar 5, 2014, at 10:52, Chris Jones <jonesc at hep.phy.cam.ac.uk> wrote:
>>> 
>>> 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 <ghleclerc at gmail.com
>>>> <mailto:ghleclerc at gmail.com>> 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
>>>>  macports-users at lists.macosforge.org
>>>>  <mailto:macports-users at lists.macosforge.org>
>>>>  https://lists.macosforge.org/mailman/listinfo/macports-users
>>>> 
>>>> 
>>>> 
>>>> 
>>>> _______________________________________________
>>>> macports-users mailing list
>>>> macports-users at lists.macosforge.org
>>>> https://lists.macosforge.org/mailman/listinfo/macports-users
>> 