| commit | e170d1ac8d62670f03eee7d7b7ef9a055754bacc | [log] [tgz] |
|---|---|---|
| author | Tom Cherry <tomcherry@google.com> | Fri May 01 16:45:25 2020 -0700 |
| committer | Tom Cherry <tomcherry@google.com> | Mon May 04 10:02:51 2020 -0700 |
| tree | ae0a68d722148890c20fd7d2c519fb93d74424f3 | |
| parent | 1a12ae3a256d4d8a0ad08d1ed5e37d7178705287 [diff] |
logd: don't use SIGHUP to reinitialize It doesn't look like there are any users, since there is a much better mechanism, `logd --reinit` that exists for this behavior. The settings app and init.rc use that mechanism and they are the two major clients that force logd to reinitialize. This saves us from creating a thread and marginally cleans up main.cpp. Test: log reinitialization works Change-Id: Icdb56b6f59adbba82812231a4f3a6ffd1a7955fc