Date: Mon, 8 Feb 2010 11:03:27 -0500 From: jhell <jhell@DataIX.net> To: "O. Hartmann" <ohartman@zedat.fu-berlin.de> Cc: freebsd-questions@freebsd.org, freebsd-ports@freebsd.org Subject: Re: net/samba34: after upgrade from samba33 -> samba34 no client can connect to samba34-server anymore! Message-ID: <alpine.BSF.2.00.1002081101100.16894@pragry.qngnvk.ybpny> In-Reply-To: <4B6FF8D0.8030208@zedat.fu-berlin.de> References: <4B6FF8D0.8030208@zedat.fu-berlin.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 8 Feb 2010 06:43, ohartman@ wrote: > After upgrading from samba33 to samba34 from most recent ports, no Windows_XP > and Windows_7 client is capable of connecting to the samba server anymore! I > use the same config as before, did a testparm (it shows this ahaead: > Load smb config files from /usr/local/etc/smb.conf > max_open_files: sysctl_max (11095) below minimum Windows limit (16384) > rlimit_max: rlimit_max (11095) below minimum Windows limit (16384) > ). > I have no idea what's going wrong. The authentication is done via LDAP. Using > samab33 works without problem. > > Regards, > Oliver > Add to /boot/loader.conf: kern.maxfiles="16384" Reboot. As for the rlimit sysctl I have no clue which sysctl configures that but seeing as they are of both the same value I would assume that it might be auto configured by maxfiles. Best of luck and let us know how it turned out. -- jhell
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1002081101100.16894>