| commit | 508ae9d92fd6d91fa7b13e116780ed4be2c8693e | [log] [tgz] |
|---|---|---|
| author | Peter Qiu <zqiu@google.com> | Tue Sep 29 10:30:48 2015 -0700 |
| committer | Peter Qiu <zqiu@google.com> | Tue Sep 29 10:32:31 2015 -0700 |
| tree | 53e64fa7df9b9290ada5983d26cf6720120e698e | |
| parent | fbfbad06ecb343c1e79f29c30021b68d23f68471 [diff] |
Do not daemonize (fork) the daemon process
When starting the daemon using an init system, the environment setup
is already being handled by the init system, so there is no need
to daemonize the daemon process create such setup.
By daemonizing the daemon process, it spawns off a new process to
run the daemon and terminates the current process. This causes
a problem with the init system, where it thinks that the daemon
failed to start. We were able to work around it on Chrome OS's
upstart script by adding the forking expectation in the init
scritp ("expect fork"), but there is not such workaround on
Android's init system.
Fix it by removing the daemonize call (daemon()) and remove the
the forking expectation on Chrome OS's init script.
Bug: 24412675
TEST=start/stop shill on Chrome OS device
Change-Id: Ib584e52f13946b2d18692e85ff55f86d22022505