Date: Tue, 24 Oct 2000 14:52:50 -0400 From: Michael Lucas <mwlucas@blackhelicopters.org> To: Breen Ouellette <the.man@breeno.net> Cc: ports@FreeBSD.ORG Subject: Re: FreeBSD Port: samba-2.0.7 Message-ID: <20001024145250.A69416@blackhelicopters.org> In-Reply-To: <000601c03ddc$9d98a520$050210ac@tao>; from the.man@breeno.net on Tue, Oct 24, 2000 at 11:05:21AM -0600 References: <000601c03ddc$9d98a520$050210ac@tao>
next in thread | previous in thread | raw e-mail | index | archive | help
Hello, For this sort of question, you'd be better off asking questions@freebsd.org, or the Samba support list. If the port wouldn't build, you'd want to check here. Regards, Michael On Tue, Oct 24, 2000 at 11:05:21AM -0600, Breen Ouellette wrote: > Hi, > > Sorry to bother you. I have looked around in the newsgroups and have not found an answer to this problem. Using FreeBSD 4.1 and the Samba port, my Windows clients are often getting semaphore timeout messages. Usually if I access a file share on a Windows machine and then go back to the Samba machine it will then work. Is it possible for me to cause this behavior with a poorly written smb.conf, or is there a bug which needs to be fixed? > > -Breen Ouellette -- Michael Lucas mwlucas@blackhelicopters.org http://www.blackhelicopters.org/~mwlucas/ Big Scary Daemons: http://www.oreillynet.com/pub/q/Big_Scary_Daemons To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20001024145250.A69416>