7e47915755
It is possible for storaged to terminate due to SIGPIPE if its clients
have terminated. This is not a fatal condition from storaged's
perspective, so we ignore SIGPIPE instead.
Bug: 151581751
Test: build
Merged-In: I633780ed20908be02e5e1dea9504e140932afc8c
Change-Id: I633780ed20908be02e5e1dea9504e140932afc8c
(cherry picked from commit
|
||
---|---|---|
.. | ||
binder/android/os | ||
include | ||
tests | ||
tools | ||
Android.bp | ||
EventLogTags.logtags | ||
main.cpp | ||
OWNERS | ||
README.properties | ||
storaged.cpp | ||
storaged.proto | ||
storaged.rc | ||
storaged_diskstats.cpp | ||
storaged_info.cpp | ||
storaged_service.cpp | ||
storaged_uid_monitor.cpp | ||
storaged_utils.cpp | ||
uid_info.cpp |
ro.storaged.event.interval # interval storaged scans for IO stats, in seconds ro.storaged.event.perf_check # check for time spent in event loop, in microseconds ro.storaged.disk_stats_pub # interval storaged publish disk stats, in seconds ro.storaged.uid_io.interval # interval storaged checks Per UID IO usage, in seconds ro.storaged.uid_io.threshold # Per UID IO usage limit, in bytes