b6bee33182
if ro.logd.timestamp or persist.logd.timestamp are set to the value
monotonic then liblog writer, liblog printing and logd all switch to
recording/printing monotonic time rather than realtime. If reinit
detects a change for presist.logd.timestamp, correct the older entry
timestamps in place.
ToDo: A corner case condition where new log entries in monotonic time
occur before logd reinit detects persist.logd.timestamp, there
will be a few out-of-order entries, but with accurate
timestamps. This problem does not happen for ro.logd.timestamp
as it is set before logd starts.
NB: This offers a nano second time accuracy on all log entries
that may be more suitable for merging with other system
activities, such as systrace, that also use monotonic time. This
feature is for debugging.
Bug: 23668800
Change-Id: Iee6dab7140061b1a6627254921411f61b01aa5c2
39 lines
2.5 KiB
Text
39 lines
2.5 KiB
Text
The properties that logd responds to are:
|
|
|
|
name type default description
|
|
logd.auditd bool true Enable selinux audit daemon
|
|
logd.auditd.dmesg bool true selinux audit messages duplicated and
|
|
sent on to dmesg log
|
|
logd.klogd bool depends Enable klogd daemon
|
|
logd.statistics bool depends Enable logcat -S statistics.
|
|
ro.config.low_ram bool false if true, logd.statistics & logd.klogd
|
|
default false
|
|
ro.build.type string if user, logd.statistics & logd.klogd
|
|
default false
|
|
persist.logd.logpersistd string Enable logpersist daemon, "logcatd"
|
|
turns on logcat -f in logd context
|
|
persist.logd.size number 256K Global default size of the buffer for
|
|
all log ids at initial startup, at
|
|
runtime use: logcat -b all -G <value>
|
|
persist.logd.size.main number 256K Size of the buffer for the main log
|
|
persist.logd.size.system number 256K Size of the buffer for the system log
|
|
persist.logd.size.radio number 256K Size of the buffer for the radio log
|
|
persist.logd.size.event number 256K Size of the buffer for the event log
|
|
persist.logd.size.crash number 256K Size of the buffer for the crash log
|
|
persist.logd.filter string Pruning filter to optimize content,
|
|
default is ro.logd.filter or
|
|
"~!" which means to prune the oldest
|
|
entries of chattiest UID. At runtime
|
|
use: logcat -P "<string>"
|
|
persist.logd.timestamp string The recording timestamp source. Default
|
|
is ro.logd.timestamp. "m[onotonic]" is
|
|
the only supported key character,
|
|
otherwise assumes realtime.
|
|
|
|
NB:
|
|
- Number support multipliers (K or M) for convenience. Range is limited
|
|
to between 64K and 256M for log buffer sizes. Individual log buffer ids
|
|
such as main, system, ... override global default.
|
|
- Pruning filter is of form of a space-separated list of [~][UID][/PID]
|
|
references, where '~' prefix means to blacklist otherwise whitelist. For
|
|
blacklisting, UID may be a '!' to instead reference the chattiest client.
|