Ooops. No, you a re asking about tasks, not threads. That is easier. The answer is no: One task exiting has not effect at all any other tasks.
In Linux, you can use the kill command to signal an entire process group, but that the last time I looked, there was no support for process groups in NuttX On Sun, Jan 15, 2023 at 7:59 PM Gregory Nutt <spudan...@gmail.com> wrote: > Xaio Xiang problem will know the current behavior better then me, But I > think you need: only pthread support. See use of HAVE_GROUP_MEMERS in > sched/task/exit.c. see include/nuttx/sched.h for definition of > HAVE_GROUP_MEMBERS. (seems to depend only on phtreads). > > > > On Sun, Jan 15, 2023 at 5:25 PM Alan C. Assis <acas...@gmail.com> wrote: > >> Dear NuttXers, >> >> I want to know if there are some hidden configuration that forces all >> children to die when the father task die. >> >> Currently only teh main task dies: >> >> nsh> family & >> >> nsh> ps >> PID GROUP PRI POLICY TYPE NPX STATE EVENT SIGMASK STACK >> COMMAND >> ... >> 27 27 100 RR Task --- Waiting Signal 00000000 004032 >> family >> 28 28 100 RR Task --- Waiting Semaphore 00000000 >> 004032 child1_daemon >> 29 29 100 RR Task --- Waiting Signal 00000000 >> 004032 child2_daemon >> 30 30 100 RR Task --- Waiting Signal 00000000 >> 001984 child3_daemon >> >> nsh> kill 27 >> nsh> ps >> PID GROUP PRI POLICY TYPE NPX STATE EVENT SIGMASK STACK >> COMMAND >> ... >> 28 28 100 RR Task --- Waiting Signal 00000000 >> 004032 child1_daemon >> 29 29 100 RR Task --- Waiting Signal 00000000 >> 004032 child2_daemon >> 30 30 100 RR Task --- Waiting Signal 00000000 >> 001984 child3_daemon >> >> I could setup a signal handling to handle the kill signal in the main >> task and use it to change the value of some conditional variable that >> maintain the threads loop of each child running, this is is an option, >> but maybe there are better option. >> >> Please let me know how you are solving this issue. >> >> BR, >> >> Alan >> >
