| commit | 987671920cec1d7148b010d78628c15d2f662861 | [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 | 4906083cdd38a7fbc71294d6ab87d7c9d3e0e4a9 | |
| parent | 04ad458e01dc340bb99e9f7150e13b9cce43d860 [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