Lines Matching refs:engine

121 for update checks to the update engine. The details of how requests are passed
122 to the update engine is system dependent, but in Chrome OS it is D-Bus.  Look at
125 There are many resiliency features embedded in the update engine that makes auto
128 *   If the update engine crashes, it will restart automatically.
141 The core update engine code base in a Chromium OS checkout is located in
150 business. Within the update engine daemon, [UpdateManager] has the
187 update engine and happen in the background. Interactive updates, on the other
232 `/var/log/update_engine` after a few restarts of the update engine or after the
263 rest of the update engine tools.
439 restart update-engine # with a dash not underscore.
545 When changing the update engine source code be extra careful about these things:
551 engine client. So for example, removing or not passing arguments in the metadata
563 When creating a change in the update engine, think about 5 years from now:
586 The current update engine code base is used in many projects like Android. We
588 or other systems that share the update engine code. Whenever landing a change,