From: Marc G. <gr...@at...> - 2009-12-27 10:18:46
|
----- "Gordan Bobic" <go...@bo...> wrote: > Gordan Bobic wrote: > > On 26/12/2009 21:44, Marc Grimme wrote: > > > And just to confirm, I used the same binary on another machine > (standalone, no OSR or clustering), and it works exactly as expected > (prints out what processes it is killing). That means that whatever > causes killall5 to go away and never return is specific to glfs+OSR > (since killall5 works fine on my gfs+OSR clusters). I'm not sure where > > to even begin debugging this, though, so any ideas would be welcome. You might want to try to start it with strace. I recall something that under some environments the browsing through /proc which is done by killall5 freezes. And I think this is done before killing. Somehow what does not work is a stat call on some /proc files within /proc/<pid>. I don't recall exactly but I have something like this in mind. If you have found the pid that causes the problem perhaps we get some new ideas on how to handle this behaviour. Marc. |