Re: Interpreting Samba messages

2003-08-20 Thread Jonathan Chen
On Thu, Aug 21, 2003 at 12:26:27AM -0400, Bob Hall wrote:

[...]
 Samba works fine, so this doesn't seem to be a problem. But I'm 
 puzzled, probably because I don't know much about this. I'm guessing 
 that the error message occurs because inetd got to the port first. 
 But I thought that binding to a port was a prerequesite for listening 
 at the port. So if binding failed, why is nmbd listening at *:137?

If you installed samba via the port, you *don't* need to make changes
to /etc/inetd.conf. The port installs a startup script that invokes
persistent smbd and nmbd deamons on startup.

So what you're seeing is a conflict between the inetd.conf setup and
the persistent daemon setup. I'd recommend that you take out the
entries in /etc/inetd.conf.

Cheers.
-- 
Jonathan Chen [EMAIL PROTECTED]
--
  Computers are like air conditioners.
  They stop working when you open Windows.
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]


Re: Interpreting Samba messages

2003-08-20 Thread Bob Hall
On Thu, Aug 21, 2003 at 04:37:29PM +1200, Jonathan Chen wrote:
 So what you're seeing is a conflict between the inetd.conf setup and
 the persistent daemon setup. I'd recommend that you take out the
 entries in /etc/inetd.conf.

You're right. Thanks.

Bob Hall
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to [EMAIL PROTECTED]