Hmm, you are right but I cannot find a process that would correspond to the 
children of any of these. These are all the processes for my username:

ps -elf | grep becsekba
4 S root      12129  17897  0  80   0 - 24867 SyS_po 14:35 ?        00:00:00 
sshd: becsekba [priv]
4 S becsekba  12131      1  0  80   0 - 10564 SyS_ep 14:35 ?        00:00:00 
/usr/lib/systemd/systemd --user
5 S becsekba  12132  12131  0  80   0 - 35030 sigtim 14:35 ?        00:00:00 
(sd-pam)
5 S becsekba  12133  12129  0  80   0 - 24867 core_s 14:35 ?        00:00:00 
sshd: becsekba@pts/107
0 S becsekba  12134  12133  0  80   0 -  7158 wait   14:35 pts/107  00:00:00 
-bash
4 S root      61763  17897  0  80   0 - 24868 SyS_po 15:13 ?        00:00:00 
sshd: becsekba [priv]
5 S becsekba  61770  61763  0  80   0 - 24868 core_s 15:13 ?        00:00:00 
sshd: becsekba@pts/117
0 S becsekba  61771  61770  0  80   0 -  7158 wait   15:13 pts/117  00:00:00 
-bash
0 S becsekba  62696  12134  0  80   0 - 38344 wait   15:13 pts/107  00:00:00 
salloc -n 8 --time=01:00:00 -C gpu
0 S becsekba  63423  62696  0  80   0 -  7457 wait   15:14 pts/107  00:00:00 
/usr/local/bin/bash
0 S becsekba  63928  63423  0  80   0 -  4437 wait   15:14 pts/107  00:00:00 
/bin/bash /apps/daint/UES/xalt/0.7.6/bin/srun -n 8 whale-dbg -i 
IMP/RunImpact2D.i
0 S becsekba  63967  63928  0  80   0 - 76108 futex_ 15:14 pts/107  00:00:00 
/opt/slurm/16.05.8/bin/srun -n 8 whale-dbg -i IMP/RunImpact2D.i
1 S becsekba  64109  63967  0  80   0 - 24908 pipe_w 15:14 pts/107  00:00:00 
/opt/slurm/16.05.8/bin/srun -n 8 whale-dbg -i IMP/RunImpact2D.i
0 R becsekba  65858  61771 99  80   0 -  9251 -      15:15 pts/117  00:00:00 ps 
-elf
0 S becsekba  65859  61771  0  80   0 -  2637 pipe_w 15:15 pts/117  00:00:00 
grep --color=auto becsekba

The fourth column is the parent process id. So when I search for one that would 
have the parent 64109 I only find this:

$ ps -elf | grep 64109
1 S becsekba  64109  63967  0  80   0 - 24908 pipe_w 15:14 pts/107  00:00:00 
/opt/slurm/16.05.8/bin/srun -n 8 whale-dbg -i IMP/RunImpact2D.i
0 S becsekba  70319  61771  0  80   0 -  2637 pipe_w 15:16 pts/117  00:00:00 
grep --color=auto 64109

$ ps --ppid 63967
PID TTY          TIME CMD
64109 pts/107  00:00:00 srun

$ ps --ppid 64109
PID TTY          TIME CMD

and the executable name:

$ ps -elf | grep whale-dbg
0 S becsekba  63928  63423  0  80   0 -  4437 wait   15:14 pts/107  00:00:00 
/bin/bash /apps/daint/UES/xalt/0.7.6/bin/srun -n 8 whale-dbg -i 
IMP/RunImpact2D.i
0 S becsekba  63967  63928  0  80   0 - 76108 futex_ 15:14 pts/107  00:00:00 
/opt/slurm/16.05.8/bin/srun -n 8 whale-dbg -i IMP/RunImpact2D.i
1 S becsekba  64109  63967  0  80   0 - 24908 pipe_w 15:14 pts/107  00:00:00 
/opt/slurm/16.05.8/bin/srun -n 8 whale-dbg -i IMP/RunImpact2D.i
0 S becsekba  77353  61771  0  80   0 -  2637 pipe_w 15:19 pts/117  00:00:00 
grep --color=auto whale-dbg




> On 13 Jan 2017, at 15:12, Roy Stogner <royst...@ices.utexas.edu> wrote:
> 
> 
> On Fri, 13 Jan 2017, Barna Becsek wrote:
> 
>> I think these also belong to the execution:
> 
> I think you've posted backtraces for every process *except* the
> important ones.  :-D
> 
> Shouldn't there be child processes of those srun processes?  The
> children would be the ones running *your* code; that's where the
> backtrace ought to tell us something.
> ---
> Roy


------------------------------------------------------------------------------
Developer Access Program for Intel Xeon Phi Processors
Access to Intel Xeon Phi processor-based developer platforms.
With one year of Intel Parallel Studio XE.
Training and support from Colfax.
Order your platform today. http://sdm.link/xeonphi
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to