Hi Andy, where you able to solve the problem? I thought that -X option for dhcpcd will help but it did not. At some point we were starting supplicant in background "-B" and init was unable to kill it afterwards. My hope was that this is the same issue - changed pid that is unknown to init.
Regards DIma On Jan 28, 5:25 pm, AndyM <andrewdm...@gmail.com> wrote: > init.svc.dhcpcdis showing STOPPED, even though thedhcpcdprocess is > still running. > > setprop ctl.stopdhcpcddoes not stop it. > > This is a problem because when I turn wifi off, it is still running in > the background. Then when I turn wifi back on,dhcpcdtries to run > again but terminates early. I get this error: > > wlan0: flock '/data/misc/dhcp/dhcpcd-wlan0.pid': Try again > > Why isn'tdhcpcddying like it should? Is it because of the fork? > > Here are logs fordhcpcdwhen it starts normally: > > 01-28 16:47:04.992: INFO//system/bin/dhcpcd(3476): wlan0:dhcpcd4.0.1 > starting > 01-28 16:47:04.992: INFO//system/bin/dhcpcd(3476): wlan0: hardware > address = 00:1f:e1:00:00:81 > 01-28 16:47:04.992: INFO//system/bin/dhcpcd(3476): wlan0: executing `/ > system/etc/dhcpcd/dhcpcd-run-hooks', reason PREINIT > 01-28 16:47:05.014: INFO//system/bin/dhcpcd(3476): wlan0: host does > not support a monotonic clock - timing can skew > 01-28 16:47:05.014: INFO//system/bin/dhcpcd(3476): wlan0: broadcasting > for a lease > 01-28 16:47:05.014: INFO//system/bin/dhcpcd(3476): wlan0: sending > DHCP_DISCOVER with xid 0xae6fe22a, next in 3.72 seconds > 01-28 16:47:05.024: INFO//system/bin/dhcpcd(3476): wlan0: offered > 10.20.17.45 from 10.20.16.22 > 01-28 16:47:05.024: INFO//system/bin/dhcpcd(3476): wlan0: checking > 10.20.17.45 is available on attached networks > 01-28 16:47:05.024: INFO//system/bin/dhcpcd(3476): wlan0: sending ARP > probe (1 of 3), next in 1.03 seconds > 01-28 16:47:05.024: INFO//system/bin/dhcpcd(3476): wlan0: ignoring > offer of 10.20.17.45 from 10.20.16.22 > 01-28 16:47:06.072: INFO//system/bin/dhcpcd(3476): wlan0: sending ARP > probe (2 of 3), next in 1.34 seconds > 01-28 16:47:07.422: INFO//system/bin/dhcpcd(3476): wlan0: sending ARP > probe (3 of 3), next in 2.00 seconds > 01-28 16:47:07.994: ERROR/WifiHW(2141): Sending cmd: DRIVER RSSI - > 01-28 16:47:07.994: ERROR/WifiHW(2141): Sending cmd: DRIVER LINKSPEED > - > 01-28 16:47:09.432: INFO//system/bin/dhcpcd(3476): wlan0: sending > DHCP_REQUEST with xid 0xae6fe22a, next in 3.10 seconds > 01-28 16:47:09.442: INFO//system/bin/dhcpcd(3476): wlan0: acknowledged > 10.20.17.45 from 10.20.16.22 > 01-28 16:47:09.442: INFO//system/bin/dhcpcd(3476): wlan0: leased > 10.20.17.45 for 691200 seconds > 01-28 16:47:09.442: INFO//system/bin/dhcpcd(3476): wlan0: adding IP > address 10.20.17.45/24 > 01-28 16:47:09.442: INFO//system/bin/dhcpcd(3476): wlan0: adding route > to 0.0.0.0/0 via 10.20.17.1 > 01-28 16:47:09.442: INFO//system/bin/dhcpcd(3476): wlan0: executing `/ > system/etc/dhcpcd/dhcpcd-run-hooks', reason BOUND > 01-28 16:47:09.454: INFO//system/bin/dhcpcd(3476): wlan0: forking to > background > 01-28 16:47:09.454: INFO/logwrapper(3476): /system/bin/dhcpcd > terminated by exit(0) --~--~---------~--~----~------------~-------~--~----~ unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---