Kevin Grigorenko

@pshipton @keithc-ca FYI Notes: * `SIGUSR1` seems to be used internally but I couldn't find any use of `SIGUSR2` * Mimicked `sigquit.c` * Tentatively chose "sigusr" as the `-Xdump` event...

> We need a documentation issue created for this. Sure, I can do that. > > Unclear if this event needs to be part of the [SigQuit thread processing](https://github.com/eclipse-openj9/openj9/blob/1c846f2/runtime/rasdump/trigger.c#L612-L614) >...

> There are still several places that declare/use things related to SIGUSR2 that are not conditional on the enabling flag. > > I think this should be an opt-in feature:...

I thought of why `user2` wasn't being parsed: It was complaining about unresolved tokens starting at `2`, so it was resolving the `user` signal and then the `2` was left...

@keithc-ca @pshipton Updated and squashed based on feedback. ``` $ java -Xdump:java:events=user2,request=exclusive+prepwalk Hang & [1] 31864 $ kill -USR2 %1 JVMDUMP039I Processing dump event "user2", detail "" at 2022/08/01 10:02:40...

jenkins compile win jdk8

@keithc-ca Feedback processed, please re-review

Tests passed; squashed.

Running the host's `runc` shows the same issue: ``` # /host/usr/bin/runc --root /host/run/runc list load container 028ef8e5ac9c9a863e4570f5939e243ac5fe9f13a22286e395501cce2e6d0d31: systemd not running on this host, cannot use systemd cgroups manager [...] ```...

Just to add that my workaround of `chroot /host runc list` does not always work. It works fine with `oc` but not with `kubectl` (targeting the same cluster): ``` $...