ACPR/android_system_core
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Merge "Clarify the behavior about event and property triggers" am: 717ece7397

Browse source 
Original change: https://android-review.googlesource.com/c/platform/system/core/+/2319963

Change-Id: Ia5b3145651b46d9cb1f657d619cceee477c57f57
Signed-off-by: Automerger Merge Worker <android-build-automerger-merge-worker@system.gserviceaccount.com>
This commit is contained in:
Jiyong Park 2022-12-14 15:42:56 +00:00 • committed by Automerger Merge Worker
commit 00229196df
1 changed files with 14 additions and 1 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
init/README.md
View file

@ -162,6 +162,17 @@ equals `true`, then the order of the commands executed will be:
setprop e 1
setprop f 2
If the property `true` wasn't `true` when the `boot` was triggered, then the
order of the commands executed will be:
setprop a 1
setprop b 2
setprop e 1
setprop f 2
If the property `true` becomes `true` *AFTER* `boot` was triggered, nothing will
be executed. The condition `boot && property:true=true` will be evaluated to
false because the `boot` trigger is a past event.
Services
--------
@ -433,7 +444,9 @@ event trigger.
For example:
`on boot && property:a=b` defines an action that is only executed when
the 'boot' event trigger happens and the property a equals b.
the 'boot' event trigger happens and the property a equals b at the moment. This
will NOT be executed when the property a transitions to value b after the `boot`
event was triggered.
`on property:a=b && property:c=d` defines an action that is executed
at three times: