From owner-freebsd-ports Tue Oct 24 10: 7: 3 2000 Delivered-To: freebsd-ports@freebsd.org Received: from toshiro.sk.sympatico.ca (toshiro.sk.sympatico.ca [142.165.5.62]) by hub.freebsd.org (Postfix) with ESMTP id 92FA637B479 for ; Tue, 24 Oct 2000 10:07:01 -0700 (PDT) Received: from tao (hss-183-33.sk.sympatico.ca [142.165.183.33]) by toshiro.sk.sympatico.ca (8.9.3/8.9.3) with SMTP id LAA47157851; Tue, 24 Oct 2000 11:06:34 -0600 (CST) Message-ID: <000601c03ddc$9d98a520$050210ac@tao> From: "Breen Ouellette" To: Cc: Subject: FreeBSD Port: samba-2.0.7 Date: Tue, 24 Oct 2000 11:05:21 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0003_01C03DAA.4CFC4630" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0003_01C03DAA.4CFC4630 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable 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 ------=_NextPart_000_0003_01C03DAA.4CFC4630 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

Sorry to bother = you. I=20 have looked around in the newsgroups and have not found an answer to = this=20 problem. Using FreeBSD 4.1 and the Samba port, my Windows clients = are=20 often getting semaphore timeout messages. Usually if I access a = file share=20 on a Windows machine and then go back to the Samba machine it will then=20 work. Is it possible for me to cause this behavior with a poorly = written=20 smb.conf, or is there a bug which needs to be fixed?

-Breen=20 Ouellette

------=_NextPart_000_0003_01C03DAA.4CFC4630-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message