> Hello. > > I think that I found a bug/mistake/feature in init-script of glusterfs-server. > > [...] > > So init script kills both of glusterfs client and server daemons... > > [...]
Hi Stanislav / List I can confirm that I see the same behaviour here: All glusterfs processes - including the ones from local mounts - are killed by 'glusterfs-server stop'. This is with the 1.3.12-1 packages from Squeeze running something close to the setup from http://www.howtoforge.com/high-availability-storage-cluster-with-glusterfs-on-ubuntu on two Lenny hosts. As far as I can see the lines: # Wait for children to finish too if this is a daemon that forks # and if the daemon is only ever run from this initscript. # If the above conditions are not satisfied then add some other code # that waits for the process to drop all resources that could be # needed by services started subsequently. A last resort is to # sleep for some time. start-stop-daemon --stop --quiet --oknodo --retry=0/30/KILL/5 --exec $DAEMON [ "$?" = 2 ] && return 2 should simply be deleted from the init script as they are too greedy here. They appear to be there simply because the init script was created using the template in /etc/init.d/skeleton . I suggest you report the bug by running 'reportbug' on one of your glusterfs hosts and filling in the details when asked (you need the reportbug package installed for that purpose). I'm not on the debian-users list myself, so please CC me on any replies. Cheers, Jonas -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
