On Thu, 2005-05-12 at 18:40 +0200, Birger Wathne wrote: > i just had a problem that may need looking into. > > my samba processes had been killed. the init.d scripts for samba (smb > and winbind) both return a non-zero status when you try to stop the > service when it's already dead. clusvcadm couldn't stop the service > because of this non-zero status, and i was also unable to start it. > > i fixed it for now by making the stop functions in smb and winbind return 0. > > are there any accepted standards for /etc/init.d scripts? What is > supposed to happen when stopping a non-running service? in other words, > is this a samba or a cluster problem? > https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=151104 Basically, our default return was 1 if it wasn't running. The LSB says it should be 0 for the stop-case if it's not running. Also, there was a bug recently reported in which stop ordering was using the start levels: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=157248 This would cause the file systems to be unmounted before Samba -- killing it uncleanly if force-unmount was used. This is fixed in CVS. -- Lon -- Linux-cluster@xxxxxxxxxx http://www.redhat.com/mailman/listinfo/linux-cluster
