[SOLVED] pidof misses a pid sometimes

Bastian Bittorf bittorf at bluebottle.com
Thu Dec 29 07:55:54 UTC 2011


> pidof: pid:9071 no match: comm:'sh' argv0:'sh' exe:'/bin/bash'
> pidof: pid:9072 no match: comm:'busybox' argv0:'./busybox'
> exe:'/root/srcdevel/bbox/fix/busybox.t2/busybox'
> pidof: pid:9073 no match: comm:'sh' argv0:'sh' exe:'/bin/bash'
> pidof: pid:24014 no match: comm:'top' argv0:'top'
> exe:'/app/busybox-1.19.2/busybox'
> found a pid, which pidof did'nt see: 9073 -> wget
> 
> In other words, when pidof was looking at process 9073, it was
> still a
> shell process -
> IOW, the syscall to execute wget did not happen yet.

Thank you very much for your debugging-work. This race/situation
(very slow fork), was till now unbelieveable to me...

bye, Bastian



More information about the busybox mailing list