Comment 2 for bug 1712288

Hi,

yes, I expect children of children to be included in this list too. By "children" I mean new process that run under the current, child or another profile.

The idea is - allow parent send signal to any children or children of children, but deny send signal to process with same peer started by another process. So, we could have 3 options:
1) signal to any processes;
2) signal to children processes only;
3) signal to specific peer only.

For example, I have qgit profile. qgit have configurable option for editor and diff programs (qgit should be able send signal "term" to them). The best solution could be signal to children processes only, but we don't have such option, so, since I use another profiles for editor and diff programs, I forced to use list of signal by peer that could be used as editor or diff programs... and allow qgit terminate any instance of editor or diff programs.