*** This bug is a duplicate of bug 180493 ***
https://bugs.launchpad.net/bugs/180493
an effective workaround is to have a small script at /etc/network/if-
up.d/start-samba.sh that simply contains the lines:
#!/bin/bash
/etc/init.d/samba restart
--
samba: nmbd no longer starts automatically
*** This bug is a duplicate of bug 180493 ***
https://bugs.launchpad.net/bugs/180493
On Tue, Jan 22, 2008 at 11:43:49PM -, phirestalker wrote:
UPDATE: the S92 fix does not work all the time there is seriously
something else wrong here for the network to STILL not be up by S92.
The
UPDATE: the S92 fix does not work all the time there is seriously
something else wrong here for the network to STILL not be up by S92.
--
samba: nmbd no longer starts automatically after gutsy upgrade
https://bugs.launchpad.net/bugs/177802
You received this bug notification because you are a
ok I think if I change one number in postinst in the deb file it will
probably start without problem I will try editing it and then
reinstalling.
** Attachment added: modified postinst
http://launchpadlibrarian.net/11319207/postinst
--
samba: nmbd no longer starts automatically after gutsy
alright that didn't work, it looks like dhcdbd starts too late in the
game still even thought it starts at S24 which is before networking,
networkmanager tries at least 25 times to load eth0 before dhcdbd starts
allowing networkmanager to finish. I'm not sure what to try next,
instead of messing
I moved samba to friggin S70 and now networkmanager gets it's address
EVEN LATER?!?!?! what the hell is going on? I'm going to reboot one more
time with S70 as it may have been a fluke, better yet I'll shut down for
a few seconds to let the networking equipment realize I'm gone before
booting back
ok fixed and working with S92 this seems like an ugly workaround for
now, as the problem is really caused by the interaction of dhcdbd and
networkmanager. As I mentioned before dhcdbd starts S24 which should be
WAY before S50 where I moved samba to originally, I did not see any
errors which would
I found these lines in /var/log/daemon.log
Jan 9 21:57:07 localhost nmbd[6073]: [2008/01/09 21:57:07, 1]
param/loadparm.c:lp_do_parameter(3517)
Jan 9 21:57:07 localhost nmbd[6073]: WARNING: The printer admin option is
deprecated
Jan 9 21:57:07 localhost nmbd[6094]: [2008/01/09 21:57:07,
samba is at S20 and dhcdbd is S24 so it seems as though samba is indeed
trying to use a network that is not yet configured.
--
samba: nmbd no longer starts automatically after gutsy upgrade
https://bugs.launchpad.net/bugs/177802
You received this bug notification because you are a member of
I have tried nmbd as root and also nmbd -D even though the man page says
-D is default operation, and one time it started and then it died
without crashing as far as I know (no crash file in /var/crash) and
another time it was running but didn't fix the problem, I imagine the
time it died was a
thank you for your report
can you detail the command you tried to use to start nmbd/smbd?
** Changed in: samba (Ubuntu)
Sourcepackagename: None = samba
--
samba: nmbd no longer starts automatically after gutsy upgrade
https://bugs.launchpad.net/bugs/177802
You received this bug notification
11 matches
Mail list logo
