It looks like the upstream patch I identified was adopted in 23.0-1, and 18.04 shipped with 23.1-1 so included it. If you can still reproduce the bug, then perhaps that patch didn't fix it, and so no fix is currently available. If you can figure out how to fix the problem, please send the patch upstream for adoption. Unfortunately with only two people reporting themselves as affected by this bug since 2016, I don't think I can justify spending more time on this, but volunteers are welcome and I will be happy to provide guidance to get a fix landed in Ubuntu's development release if they can come forward with one that has been accepted upstream.
> Unfortunately, within mpi a program cannot tell if the program was started > as: "mpiexec -n 20 my_program" or serially as "my_program". By running a > command line "pstree -s -l -p PID" prior to initializing the MPI world, I could distinguish the two different start up modi. Can you not inspect argv[0]? In any case, you don't _need_ to use pstree for that. Examine /proc/PID/cmdline, or if you want to follow parent PIDs, you can use getppid(2) or call "ps" to follow that recursively. I appreciate that the latter is just a workaround for the bug in pstree, of course, but "workaround available" does qualify lower priority. In any case, a program calling pstree to determine how it itself was called seems like a horrible hack as it is. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1629839 Title: pstree reports "/proc/xxxx: No such file or directory" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/psmisc/+bug/1629839/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
