Hi folks,
we're using the following commands in a shutdown script to end all samba processes on our archive server:
/opt/pware/samba/3.0.25a/bin/smbcontrol -s /shareddir/smb.conf nmbd shutdown
/opt/pware/samba/3.0.25a/bin/smbcontrol -s /shareddir/smb.conf smbd shutdown
But when the shutdown script comes to the point where it is to unmount the filesystems it fails and we have to perform all remaining actions manually because there are always smbd and nmbd processes remaining active that we have to kill first blocking the filesystem ...
Is there any way to prevent this from happening ? Maybe perform some kind of forces smbcontrol shutdown or a way to script a kill on everything that's named smbd and nmbd ?
Regards
Thomas
we're using the following commands in a shutdown script to end all samba processes on our archive server:
/opt/pware/samba/3.0.25a/bin/smbcontrol -s /shareddir/smb.conf nmbd shutdown
/opt/pware/samba/3.0.25a/bin/smbcontrol -s /shareddir/smb.conf smbd shutdown
But when the shutdown script comes to the point where it is to unmount the filesystems it fails and we have to perform all remaining actions manually because there are always smbd and nmbd processes remaining active that we have to kill first blocking the filesystem ...
Is there any way to prevent this from happening ? Maybe perform some kind of forces smbcontrol shutdown or a way to script a kill on everything that's named smbd and nmbd ?
Regards
Thomas