Did anyone notice that in the 7/13 build, when ENM scripts complete, nwamd is terminated. svc.configd subsequently start nwamd again.
Looking at the debug logs, I see that the signal handler catches SIGCHLD. since we don't specify how to handle this signal, it terminates nwamd with graceful_shutdown(). Previously, no such SIGCHLD was caught by nwamd. Discussion on the IRC #onnv lead me to CR "6857047 sigwait malfunctions for system-generated SIGCHLD signals". It seems that SIGCHLD was improperly being ignored. There also a related CR "6861646 nwamd terminates prematurely in snv_119" for Phase 0.5 since it has the similar signal handling code as our gate. What's the right thing to do here? Catch SIGCHLD in main.c:sighandler() and then don't do anything?? Anurag http://monaco.sfbay/detail.jsf?cr=6857047 http://monaco.sfbay/detail.jsf?cr=6861646
