Currently Being ModeratedJul 26, 2011 10:34 AM (in response to Terence Devlin)
Thanks Terence, I checked that page, some of those processes were in that list; I also tried "man" and got some answers:
awacsd is an executable invoked by launchd to facilitate connections between devices using Back to My Mac.
special_file_handler / ubd -- for "Mobile Documents" (iCloud I suppose)
talagent provides services related to the Transparent App Lifecycle feature.
warmd controls caches used during startup and login.
However, still no idea about:
Currently Being ModeratedJul 31, 2011 2:45 AM (in response to FreeWizard)
icudt46l is one of the files used by lsboxd , i think it's used for unicode - check this site.
Currently Being ModeratedAug 9, 2011 7:55 AM (in response to FreeWizard)
lsboxd is part of the application sandbox. I think it is responsible for communicating between sandboxed processes.
I don't see librariand on my system (binary or process), could it be part of an application on yours?
There's a manual page for CVMServer, but it's pretty abstruse:
CVMServer -- Mac OS X Core Virtual Machine Server
CVMServer is a system daemon that handles generic task execution in a
It's part of the OpenGL framework, and appears to be related to running OpenCL code.
Currently Being ModeratedNov 29, 2011 5:55 AM (in response to FreeWizard)
I was recently prompted for access to my keychain for librariand and ubd. I see librariand and ubd as:
I didn't see prompts for keychain access to these processes before I enabled iCloud on that system. Afterwards, I was prompted.
A man page exists for ubd and talks vaguely about "Mobile Documents."
I suspect these are both are related to iCloud somehow. This would help explain why they are new to Lion and not present on Snow Leopard.
The name of the framework, "Ubiquity," is pretty interesting in and of itself.