Bug 109205 - Change default value of MAX_CONNECTIONS constant
Summary: Change default value of MAX_CONNECTIONS constant
Alias: None
Product: Red Hat Enterprise Linux 2.1
Classification: Red Hat
Component: samba
Version: 2.1
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Simo Sorce
QA Contact: David Lawrence
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-05 17:02 UTC by Jesus Ortega (a.k.a Nitebirdz)
Modified: 2007-11-30 22:06 UTC (History)
1 user (show)

Clone Of:
Last Closed: 2007-10-19 19:23:49 UTC

Attachments (Terms of Use)

Description Jesus Ortega (a.k.a Nitebirdz) 2003-11-05 17:02:07 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5b)

Description of problem:
The file "smbd/conn.c" contains a hard coded limitation for
connections that is causing problems with Citrix servers.

conn.c:#define MAX_CONNECTIONS 256

If there are many users connected to a Citrix Metaframe server, the
connections to shares start fo fail with the following error:

ERROR! Out of connection structures

Simply changing the value to something like 1024 and recompiling fixes
the problem, which also appears to be present in Samba 3.0 and RHEL
3.0.  Since the target market of the product is the enterprise, you
may want to consider bumping up this value.  There is an existing bug
at samba.org (see below), but I wonder if perhaps you might consider
building your RPM with this change.


Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Configure Windows system as Citrix Metaframe server
2. Configure shares over Samba

Additional info:

Comment 4 RHEL Product and Program Management 2007-10-19 19:23:49 UTC
This bug is filed against RHEL2.1, which is in maintenance phase.
During the maintenance phase, only security errata and select mission
critical bug fixes will be released for enterprise products.  Since
this bug does not meet that criteria, it is now being closed.

For more information of the RHEL errata support policy, please visit:

If you feel this bug is indeed mission critical, please contact your
support representative.  You may be asked to provide detailed
information on how this bug is affecting you.

Note You need to log in before you can comment on or make changes to this bug.