blob: 6200d3ee54366d7ff0236745e6796d0de919f514 [file] [log] [blame]
Mark Salyzyn7260a5c2014-04-21 07:41:28 -07001The properties that logd responds to are:
2
3name type default description
Sami Tolvanena742d102016-06-14 18:04:43 +00004ro.logd.auditd bool true Enable selinux audit daemon
Mark Salyzyn9c66a582015-12-14 16:40:12 -08005ro.logd.auditd.dmesg bool true selinux audit messages duplicated and
Mark Salyzyn7260a5c2014-04-21 07:41:28 -07006 sent on to dmesg log
Mark Salyzyn9c66a582015-12-14 16:40:12 -08007persist.logd.security bool false Enable security buffer.
8ro.device_owner bool false Override persist.logd.security to false
9ro.logd.kernel bool+ svelte+ Enable klogd daemon
10ro.logd.statistics bool+ svelte+ Enable logcat -S statistics.
Mark Salyzynd1f41d62016-02-09 15:49:29 -080011ro.debuggable number if not "1", logd.statistics &
Mark Salyzyn9c66a582015-12-14 16:40:12 -080012 ro.logd.kernel default false.
13persist.logd.logpersistd string Enable logpersist daemon, "logcatd"
Mark Salyzyn100658c2015-05-26 14:57:13 -070014 turns on logcat -f in logd context
Mark Salyzyn9c66a582015-12-14 16:40:12 -080015persist.logd.size number ro Global default size of the buffer for
Mark Salyzyn932f7ac2015-08-28 08:02:59 -070016 all log ids at initial startup, at
17 runtime use: logcat -b all -G <value>
Mark Salyzyn66607eb2016-01-05 08:49:44 -080018ro.logd.size number svelte default for persist.logd.size. Larger
19 platform default sizes than 256KB are
20 known to not scale well under log spam
21 pressure. Address the spam first,
22 resist increasing the log buffer.
Mark Salyzyn9c66a582015-12-14 16:40:12 -080023persist.logd.size.<buffer> number ro Size of the buffer for <buffer> log
24ro.logd.size.<buffer> number svelte default for persist.logd.size.<buffer>
25ro.config.low_ram bool false if true, logd.statistics, logd.kernel
26 default false, logd.size 64K instead
27 of 256K.
28persist.logd.filter string Pruning filter to optimize content.
29 At runtime use: logcat -P "<string>"
Mark Salyzynbec3c3d2015-08-28 08:02:59 -070030ro.logd.filter string "~! ~1000/!" default for persist.logd.filter.
Mark Salyzyn9c66a582015-12-14 16:40:12 -080031 This default means to prune the
Mark Salyzynbec3c3d2015-08-28 08:02:59 -070032 oldest entries of chattiest UID, and
33 the chattiest PID of system
34 (1000, or AID_SYSTEM).
Mark Salyzyn9c66a582015-12-14 16:40:12 -080035persist.logd.timestamp string ro The recording timestamp source.
36 "m[onotonic]" is the only supported
37 key character, otherwise realtime.
38ro.logd.timestamp string realtime default for persist.logd.timestamp
39log.tag string persist The global logging level, VERBOSE,
40 DEBUG, INFO, WARN, ERROR, ASSERT or
41 SILENT. Only the first character is
42 the key character.
43persist.log.tag string build default for log.tag
44log.tag.<tag> string persist The <tag> specific logging level.
45persist.log.tag.<tag> string build default for log.tag.<tag>
Mark Salyzyn671e3432014-05-06 07:34:59 -070046
47NB:
Mark Salyzyn9c66a582015-12-14 16:40:12 -080048- bool+ - "true", "false" and comma separated list of "eng" (forced false if
Mark Salyzynd1f41d62016-02-09 15:49:29 -080049 ro.debuggable is not "1") or "svelte" (forced false if ro.config.low_ram is
Mark Salyzyn9c66a582015-12-14 16:40:12 -080050 true).
51- svelte - see ro.config.low_ram for details.
Mark Salyzynd1f41d62016-02-09 15:49:29 -080052- svelte+ - see ro.config.low_ram and ro.debuggable for details.
Mark Salyzyn9c66a582015-12-14 16:40:12 -080053- ro - <base property> temporary override, ro.<base property> platform default.
54- persist - <base property> override, persist.<base property> platform default.
55- build - VERBOSE for native, DEBUG for jvm isLoggable, or developer option.
56- number - support multipliers (K or M) for convenience. Range is limited
Mark Salyzyn932f7ac2015-08-28 08:02:59 -070057 to between 64K and 256M for log buffer sizes. Individual log buffer ids
58 such as main, system, ... override global default.
59- Pruning filter is of form of a space-separated list of [~][UID][/PID]
60 references, where '~' prefix means to blacklist otherwise whitelist. For
Mark Salyzynbec3c3d2015-08-28 08:02:59 -070061 blacklisting, UID or PID may be a '!' to instead reference the chattiest
62 client, with the restriction that the PID must be in the UID group 1000
63 (system or AID_SYSTEM).