Re: solution to pcmcia network problems (was Re: [Cooker] Bug reporton initscripts-7.06-3mdk)
James Sparenberg wrote: > On Fri, 2003-02-14 at 02:51, Buchan Milne wrote: > >>Probably a misconfigured samba and the fact that we start/stop smbd and >>nmbd together. So, /etc/rc.d/init.d/smb stops smbd, tries to stop nmbd >>and fails (was not running or had a name conflict or something like >>that), and since both killprocs did not succeed, it does not remove the >>lock file, so it is run again. > > > this is the hard part. Since I'm in a shutdown situation how do I check > to see if the lockfile is getting removed or not. What happens if you stop samba manually? Or if you init 1? > >>I guess we should put a check in to see if nmbd and smbd are really >>running, but it may be better to leave the error so the user knows they >>have something to fix? > > > This is the thing... what is the fix. Samba is working quite well so > I'm pretty sure the config is good. (printing shares etc are solid.) I > really don't do much more than use samba to print on a windows box at > home. > Weird ... will have to bounce a few machines to test, but I do not remember seeing this ... Buchan -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
Re: solution to pcmcia network problems (was Re: [Cooker] Bug reporton initscripts-7.06-3mdk)
James Sparenberg wrote: > One question though... what is it in Killall that tries to stop > Samba... I've noticed it first here testing 9.1 but on my 9.0 and 8.2 > boxes as well smb gets stopped nmb reports failed then once killall > starts up it then again attempts to shutdown smb and nmb again. This is > no show stopper I think I submitted the bug as a p4, but inevitably the > user who has the least understanding (or capability to understand) is > the one who panics when they see the FAILED in big read letters. Probably a misconfigured samba and the fact that we start/stop smbd and nmbd together. So, /etc/rc.d/init.d/smb stops smbd, tries to stop nmbd and fails (was not running or had a name conflict or something like that), and since both killprocs did not succeed, it does not remove the lock file, so it is run again. I guess we should put a check in to see if nmbd and smbd are really running, but it may be better to leave the error so the user knows they have something to fix? SuSE has split their init scripts for samba into one each for smbd and nmbd, mainly to allow an nmbd restart (to reregister in WINS for example) without killing smbd (and the connections). But it makes complications ... I would rather add another option to the script that just restarts nmbd ... but I have never had this problem, so I do not have a setup to test ... Buchan -- |--Another happy Mandrake Club member--| Buchan MilneMechanical Engineer, Network Manager Cellphone * Work+27 82 472 2231 * +27 21 8828820x121 Stellenbosch Automotive Engineering http://www.cae.co.za GPG Key http://ranger.dnsalias.com/bgmilne.asc 1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
