Example: <http://afk.molgen.mpg.de/mxq/mxq/job/52186272> Job: ``` job_status : FAILED host_hostname : freshwatercrocodile.molgen.mpg.de host_slots : 9 host_cpu_set : 87-95 date_end : 2024-09-10 17:15:59 (7 minutes runtime) ``` Group: ``` job_threads : 1 job_memory : 32768 MiB job_time : 60 minutes ``` Server: ``` daemon_slots : 256 daemon_memory : 979817 ``` So this job was submitted with `--processors 1` (`job_threads: 1`) but used 9 server 'slots' because of the memory constraints (32768/(979817/256)=8.56). At <https://github.molgen.mpg.de/mariux64/mxq/blob/adb6f2fb2d08963c193120a73795df5163207141/mxqd.c#L1177> it was granted 9 processors because of the number of slots. However at https://github.molgen.mpg.de/mariux64/mxq/blob/adb6f2fb2d08963c193120a73795df5163207141/mxqd.c#L1022 the code wrongly assumes that jobs with `job_threads == 1` only have one processor and uses `setrlimit(RLIMIT_CPU,...)` in that case. The referenced example job used 256 threads in one of its processes and 9 processors were able to exceed the job_time limit of 63 minutes (60 * 5%) in 7 minutes, so the process received a SIGXCPU.