nmbd doesn't want to start...

[fsvara]

while smbd does...
From swat i can start smbd, and it is reportet as running, which is correct, looking at ps -A. Then i try to start nmbd, but that doesn't work, its status just stays 'not running'. I can try to start nmbd from the command line, which lets my computer show some activity for a short time, but a look at ps -A tells me nmbd still doesn't run... It seems like it just doesn't want to...
Any ideas?

[Fandelem]

check /var/log/messages - it will say startup succeeded or give an error message.. typically on most systems you can (as root) issue the command: samba restart and it will restart both smbd and nmbd for ya.

regards,

~kyle

if you still can't get it working, post the log errors.

[fsvara]

I looked at /var/log/messages, and the last line was
something about [PAM]unix2 (me using su to become root).
Then I started smbd (./smbd) and issued a ps -A. It
was right there. I looked at /var/log/messages. There
were no new messages.
I did a ./nmbd and looked at ps -A. It wasn't there, as
always before. Then I looked at messages again, but there
was no new message. The last line still told me
that I had used su. (I have always exited vi and reloaded the
messages file)
It nmbd doesn't give me a single error message...
When I type ./smbd it shows some activity, and i get back
to the prompt after about a second. Same for nmbd. Only
it isn't there afterwards. http://www.linuxnewbie.org/ubb/frown.gif

[fsvara]

smbd didn't say startup succeeded... just silent, but it runs...
And the command samba restart doesn't work.
It the nhf it says you can issue smb restart, but
that one doesn't work either (command not found). There is no program by the name of
samba. Not in the samba bin directory, whereis which and locate, don't
find it, either.

[This message has been edited by fsvara (edited 08 December 2000).]

[fsvara]

ok, I've found several strange things.
For example, the smb.conf that swat writes is not in /etc/smb.conf, but in /usr/local/samba/lib/smb.conf. Does this have something to do with the new version of samba, 2.0.7? And nmbd and smbd don't send their errors to /var/log/messages, but to /usr/local/samba/var/log.smb for smbd and log.nmb for nmbd. In log.nmb, I've seen that nmbd has problems with the interfaces line in smb.conf.
I removed that line and now everything works. The win computers can access my shares through the network neighbourhood.
Now my question is 'What is the interfaces line for, if samba works perfectly without it?'