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


Click here to return to the 'One potential fix for a Parallels-related slowdown' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
One potential fix for a Parallels-related slowdown
Authored by: ghay on Jul 18, '07 08:23:20AM

I'm curious, is there a marked improvement over using the built-in pause function of parallels?



[ Reply to This | # ]
One potential fix for a Parallels-related slowdown
Authored by: maddys_daddy on Jul 18, '07 12:37:24PM
The hints author explicitly stated that he experiences this problem when Parallels is not running. Thus the built in "Pause" feature of parallels isn't apropos here.

[ Reply to This | # ]
One potential fix for a Parallels-related slowdown
Authored by: jsutton on Jul 25, '07 11:18:30AM

THis hint is referring to a process by the name of "llipd" that runs even when parallels is not running. (it is a daemon... meaning it run all the time. when you installed parallels, it probably told you to restart... when you restarted, this llipd daemon ran and remained running).

The pause button in the parallels interface is just a way to "pause" the state of the virtual OS you are running. It saves the state and allows you to resume the state when you unpause it.

This pause is different than running the "kill -stop" command. the kill -stop command is a os x system command to tell the llipd daemon to pause its activity. When you run the kill -stop command, the llipd daemon is still "running" but doesn't ask the system for processor time because it is running in a paused state.



[ Reply to This | # ]