3 ms·
IIRC Chrome installs some kind of persistent daemon that is entirely separate from the application itself. Keystone Agent or something like that.
by frou_dh 8y ago
IIRC Chrome installs some kind of persistent daemon that is entirely separate from the application itself. Keystone Agent or something like that.
- ultrafez 8y agoI've come across this before. I don't know what its full responsibilities are, but I know it's part of the Chrome update process. I came across it when I was trying to get two totally separate Chrome installs working on one machine (using https://github.com/djbclark/chrome-schismator https://github.com/djbclark/chrome-schismator), in such a way that they can run in parallel, update in parallel, each totally isolated from one another. It seems as though it's not possible to have two Chrome installs update themselves separately due to the Keystone application only being able to store one reference to a Chrome install at a time, meaning that the other Chrome instance never detects that it's out of date.