Mailinglist Archive: opensuse (1558 mails)
| < Previous | Next > |
[opensuse] Samba won't start because of Vmware Networking
- From: Istvan Gabor <suseuser04@xxxxxxx>
- Date: Thu, 27 Aug 2009 14:25:45 +0200
- Message-id: <2a08a71a.5e4595f.4a967b49.7ea37@xxxxx>
Hello:
I have a very similar problem to this one:
http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware.html
Excerpt from the above thread:
"smb and nmb boot scripts fail to start smbd and nmbd.
Samba is configured to only listen to the host-only network interface
from VMware at vmnet1:192.168.230.1. I think what
happens is that the vmnet1 interface doesn't appear until after the smb
and nmb scripts run, so the smbd/nmbd die.
However, when I manually do /etc/init.d/smb restart after my system is
fully up, then Samba starts just fine and works too.
How to make Samba wait a bit for the vmnet1 interface to appear?"
There is no working solution at the above site, so I am asking the question
here.
Thanks,
Istvan
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
I have a very similar problem to this one:
http://fixunix.com/networking/526438-problem-samba-wont-start-because-vmware.html
Excerpt from the above thread:
"smb and nmb boot scripts fail to start smbd and nmbd.
Samba is configured to only listen to the host-only network interface
from VMware at vmnet1:192.168.230.1. I think what
happens is that the vmnet1 interface doesn't appear until after the smb
and nmb scripts run, so the smbd/nmbd die.
However, when I manually do /etc/init.d/smb restart after my system is
fully up, then Samba starts just fine and works too.
How to make Samba wait a bit for the vmnet1 interface to appear?"
There is no working solution at the above site, so I am asking the question
here.
Thanks,
Istvan
--
To unsubscribe, e-mail: opensuse+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse+help@xxxxxxxxxxxx
| < Previous | Next > |