From owner-freebsd-questions Tue Oct 24 22:14:55 2000 Delivered-To: freebsd-questions@freebsd.org Received: from toshiro.sk.sympatico.ca (toshiro.sk.sympatico.ca [142.165.5.62]) by hub.freebsd.org (Postfix) with ESMTP id 75B6237B479 for ; Tue, 24 Oct 2000 22:14:49 -0700 (PDT) Received: from tao (hss-180-144.sk.sympatico.ca [142.165.180.144]) by toshiro.sk.sympatico.ca (8.9.3/8.9.3) with SMTP id XAA48184971 for ; Tue, 24 Oct 2000 23:14:47 -0600 (CST) Message-ID: <001201c03e42$58517170$050210ac@tao> From: "Breen Ouellette" To: Subject: Samba semaphore timeout problems Date: Tue, 24 Oct 2000 23:13:12 -0600 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_000D_01C03E0F.FB6A1980" 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-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is a multi-part message in MIME format. ------=_NextPart_000_000D_01C03E0F.FB6A1980 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Hi, I am currently getting semaphore timeout messages when my Windows = based clients try to access Samba (2.0.7) on the FreeBSD box (4.1). Is = it possible that my smb.conf is causing this? I will include it below. = Also, one of the shares is pointing to a ccd virtual disk which consists = of two 15GB partitions. Could this be causing problems? I will include = my cdd.conf in this message as well. =20 This behavior is erratic. Sometimes machines log in just fine, = other times no go. A machine may access the shares fine with one user, = and if someone else logs in two minutes later from the same machine they = cannot access the Samba shares. Usually, if a user cannot get to the = Samba shares, they can go read a share on a different machine, then come = back to the Samba machine and get in just fine. It is really annoying, = however, especially waiting for mapped drives to time out when logging = in. I didn't experience these problems in 4.0 with Samba 2.0.6, but my = smb.conf has changed since then, plus I wasn't using ccd then. If I = have to, I will return to 4.0/2.0.6, but this seems like backtracking, = which I don't like to do. --smb.conf: [global] #Server setup encrypt passwords =3D yes local master =3D no netbios name =3D JEEVES server string =3D workgroup =3D BREENO #Network configuration allow hosts =3D 172.16.2. localhost #Global share values browseable =3D no guest account =3D nobody guest ok =3D yes guest only =3D yes hide dot files =3D yes invalid users =3D root map to guest =3D Bad User security =3D user writeable =3D no #Logging options debug timestamp =3D yes log level =3D 2 log file =3D /var/log/samba.log.%m max log size =3D 50 [homes] comment =3D %U's home folder guest ok =3D no guest only =3D no inherit permissions =3D yes valid users =3D lex writeable =3D yes [Music] browseable =3D yes comment =3D Music folder path =3D /export/music [Upload] browseable =3D yes comment =3D Upload folder inherit permissions =3D yes path =3D /export/upload writeable =3D yes [Optra] browseable =3D yes comment =3D Lexmark Optra E310 printer path =3D /var/spool/samba print command =3D /usr/bin/lpr -r %s printable =3D yes printer =3D lp printing =3D BSD --EOF --ccd.conf: # # /etc/ccd.conf # # ccd ileave flags compnent devices ccd0 0 none /dev/ad0s2e /dev/ad3s2e --EOF Thanks in advance for any help. -Breen Ouellette ------=_NextPart_000_000D_01C03E0F.FB6A1980 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable

Hi,

I am currently = getting semaphore=20 timeout messages when my Windows based clients try to access Samba = (2.0.7) on=20 the FreeBSD box (4.1). Is it possible that my smb.conf is causing=20 this? I will include it below. Also, one of the shares is = pointing=20 to a ccd virtual disk which consists of two 15GB partitions. Could = this be=20 causing problems? I will include my cdd.conf in this message = as=20 well.

This behavior is = erratic. =20 Sometimes machines log in just fine, other times no go. A machine = may=20 access the shares fine with one user, and if someone else logs in two = minutes=20 later from the same machine they cannot access the Samba shares. = Usually,=20 if a user cannot get to the Samba shares, they can go read a share on a=20 different machine, then come back to the Samba machine and get in just=20 fine. It is really annoying, however, especially waiting for = mapped drives=20 to time out when logging in.

I didn't experience = these=20 problems in 4.0 with Samba 2.0.6, but my smb.conf has changed since = then, plus I=20 wasn't using ccd then. If I have to, I will return to 4.0/2.0.6, = but this=20 seems like backtracking, which I don't like to do.

--smb.conf:

[global]
#Server = setup
encrypt=20 passwords =3D yes
local master =3D no
netbios name =3D = JEEVES
server string =3D
workgroup =3D = BREENO

#Network = configuration
allow hosts =3D=20 172.16.2. localhost

#Global share = values
browseable =3D=20 no
guest account =3D nobody
guest ok =3D = yes
guest only =3D=20 yes
hide dot files =3D yes
invalid users =3D = root
map to=20 guest =3D Bad User
security =3D user
writeable =3D = no

#Logging options
debug = timestamp =3D=20 yes
log level =3D 2
log file =3D=20 /var/log/samba.log.%m
max log size =3D 50

[homes]
comment =3D %U's home=20 folder
guest ok =3D no
guest only =3D = no
inherit=20 permissions =3D yes
valid users =3D lex
writeable =3D=20 yes

[Music]
browseable =3D = yes
comment=20 =3D Music folder
path =3D /export/music

[Upload]
browseable =3D = yes
comment=20 =3D Upload folder
inherit permissions =3D yes
path =3D = /export/upload
writeable =3D yes

[Optra]
browseable =3D = yes
comment=20 =3D Lexmark Optra E310 printer
path =3D = /var/spool/samba
print=20 command =3D /usr/bin/lpr -r %s
printable =3D = yes
printer =3D=20 lp
printing =3D BSD
--EOF

--ccd.conf:

#
# /etc/ccd.conf
#

# = ccd ileave flags compnent=20 devices
ccd0 0 none /dev/ad0s2e=20 /dev/ad3s2e
--EOF

Thanks in advance = for any=20 help.

-Breen=20 Ouellette

------=_NextPart_000_000D_01C03E0F.FB6A1980-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message