TimJTi commented on issue #16135: URL: https://github.com/apache/nuttx/issues/16135#issuecomment-2887266118
Stumbled across this issue while using dhcpd as a template for a similar daemon. At present, the daemon loop does nothing except sleep for 100ms (until I get the structure in place and add actual code). In my case I am using a USB CDC-NCM connection, and this daemon with be used for network related stuff. If I start and stop my daemon before I have plugged in my USB, the CDC-NCM session is never initiated. If I start/stop *after* the first successful CDC-NCM session all is good. I think the kill() call is to blame perhaps but I am not experienced enough to know why of if this could be the case. I will be trying intercepting the signal and doing a better controlled shut down of the daemon before "killing" the task outright. I did try a different signal (35 - a random choice) but no difference. No idea if this helps here but thought I'd throw it in as it seemed too similar to just be a coincidence; and suggests it may be nothing whatsoever to do with DHCP(D) itself (since my actual daemon does nothing!!). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@nuttx.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
