Joan Lledó, le dim. 07 mars 2021 20:08:21 +0100, a ecrit: > is not there any process that kills the arbiter after a while of not > being used?
That shouldn't be happening. > and how could I know who is sending the SIGKILL? How do you notice that it's a SIGKILL? You could e.g. put mach_prints in glibc's sysdeps/mach/hurd/kill.c's SIGKILL case. Possibly better also add a mach_print in hurd/hurdsig.c SIGKILL on _hurd_orphaned. Samuel
