Am 29.12.2011 08:55, schrieb Bastian Bittorf: >> 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...
If something that is timing-dependent can go wrong, it will -- sooner or later, and whether you believe it possible or not :) _______________________________________________ busybox mailing list [email protected] http://lists.busybox.net/mailman/listinfo/busybox
