Hi,
The vote closes now as over 72hr have passed. The vote PASSES with 4
4 (+1 binding) vote from the PMC,
0 (+0 non-binding) votes from the developer community,
No further +1, 0 or -1 votes.
The vote thread:
[1] https://lists.apache.org/thread/0gk0svgw9o8s9zk55mwbomwsvm55ncqb
The release is acce
+1, test with sim and spresense
./nuttx/tools/checkrelease.sh --release 12.0.0-RC1
Downloading release files from
https://dist.apache.org/repos/dist/dev/nuttx/12.0.0-RC1/
gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
gpg:
Yes, there is task group concept and support by kill API directly:
https://pubs.opengroup.org/onlinepubs/009604499/functions/kill.html
If *pid* is negative, but not -1, *sig* shall be sent to all processes
(excluding an unspecified set of system processes) whose process group ID
is equal to the ab
If you kill a process in Linux. All of its child processes should continue
to run as orphan processes. This is the Linux compatible behavior for the
case that Alan presented.
On Sun, Jan 15, 2023 at 10:31 PM Gregory Nutt wrote:
> That wouldn’t be consistent with how Linux works, would it? I'm
That wouldn’t be consistent with how Linux works, would it? I'm not an
expert on this topic and I am sure that other people on this list know more
about this than me. My understanding is that Linux has "session leaders"
which correspond to login sessions. For each terminal opened by the
session
If CONFIG_SIG_DEFAULT, the kernel will terminate all child pthreads, but
not child tasks.
We can extend kill to support -P flag like pkill:
https://linux.die.net/man/1/pkill
-P ppid,...
Only match processes whose parent process ID is listed.
On Mon, Jan 16, 2023 at 10:14 AM Gregory Nutt wrote:
>
+1, test with sim:
./tools/checkrelease.sh --release 12.0.0-RC1
Downloading release files from
https://dist.apache.org/repos/dist/dev/nuttx/12.0.0-RC1/
gpg: directory '/tmp/nuttx-checkrelease/.gnupg' created
gpg: keybox '/tmp/nuttx-checkrelease/.gnupg/pubring.kbx' created
gpg: /tmp/nuttx-checkrelea
he
> 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.
>
The question is confusing because it asks about killing other threads (aka
pthreads) when the main (task) exits. But the example shows only t
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
N
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 A
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 TYPENPX STATEEVENT SIGMASK STACK COMMAND
...
2727 100 RR
11 matches
Mail list logo