Re: [OSR-devel] /etc/xkillallprocs and /etc/xkillall_procs

[Marc G. <gr...@at...>]

Hi Gordan,
sorry for taking that long.
On Tuesday 16 June 2009 16:53:02 Gordan Bobic wrote:
> What is the difference between these two files? I noticed that
> /etc/xkillallprocs got clobbered after a reboot, and the two lines I added
> to it (glusterfs and glusterfsd) got removed. On shutdown, with the file
Yes they got removed. Basically they should be built automatically.
The procs are got from a function called {rootfs}_get_userspace_procs. In your 
case it should be glusterfs_userspace_procs.
For gfs (rhel5) it looks as follows:

function gfs_get_userspace_procs {
  local clutype=$1
  local rootfs=$2

  echo -e "aisexec \n\
ccsd \n\
fenced \n\
gfs_controld \n\
dlm_controld \n\
groupd \n\
qdiskd \n\
clvmd"
}


> edited to add those two, shutdown with glusterfs still locks up immediately
> after "sending all processes the TERM signal". Any ideas on how to debug
> this further? My gut feeling is that glusterfs ends up getting killed and
> the machine locks up because the rootfs went away, but it's quite hard
> investigate a system in such a hung state.
Yes. It is. I always add /bin/bash(s) at every step in the relevant 
initscripts. But I would say if you get that xkillallprocs right it should 
work.

You also need the /usr/comoonics/sbin/killall binary which does not kill _ALL_ 
userproceses but can exclude the ones in i.e. /etc/xkillallprocs.

For a little backround see:
https://bugzilla.redhat.com/show_bug.cgi?id=496843
https://bugzilla.redhat.com/show_bug.cgi?id=496854
https://bugzilla.redhat.com/show_bug.cgi?id=496857
https://bugzilla.redhat.com/show_bug.cgi?id=496861

Again sorry for the late response.

But still hope that helps
Marc.


-- 
Gruss / Regards,

Marc Grimme
http://www.atix.de/               http://www.open-sharedroot.org/