>Number: 5001 >Category: general >Synopsis: Large number of site overflows frontpage extensions in Apache >1.3.3 >Confidential: no >Severity: non-critical >Priority: medium >Responsible: apache >State: open >Class: sw-bug >Submitter-Id: apache >Arrival-Date: Sun Sep 12 05:30:01 PDT 1999 >Last-Modified: >Originator: [EMAIL PROTECTED] >Organization: apache >Release: 1.3.3 >Environment: I am running SCO 5.0.4 with the SCO Development system. I have apache 1.3.3 with fronpage extension support compiled in (I did it) Everything works fine until I have more than 42 virtual web sites. If I add more than 42 then when I start the httpd daemon the frontpage extensions no longer work but the standard httpd (apache 1.3.3) engine still works for regular sites. Can you point me in the direction as to where I can fix this problem.
Thank's Guy St-Amant [EMAIL PROTECTED] >Description: I am running SCO 5.0.4 with the SCO Development system. I have apache 1.3.3 with fronpage extension support compiled in (I did it) Everything works fine until I have more than 42 virtual web sites. If I add more than 42 then when I start the httpd daemon the frontpage extensions no longer work but the standard httpd (apache 1.3.3) engine still works for regular sites. Can you point me in the direction as to where I can fix this problem. >How-To-Repeat: >Fix: Probably some settings to increase memory space allocated for site definitions tables >Audit-Trail: >Unformatted: [In order for any reply to be added to the PR database, you need] [to include <[EMAIL PROTECTED]> in the Cc line and make sure the] [subject line starts with the report component and number, with ] [or without any 'Re:' prefixes (such as "general/1098:" or ] ["Re: general/1098:"). If the subject doesn't match this ] [pattern, your message will be misfiled and ignored. The ] ["apbugs" address is not added to the Cc line of messages from ] [the database automatically because of the potential for mail ] [loops. If you do not include this Cc, your reply may be ig- ] [nored unless you are responding to an explicit request from a ] [developer. Reply only with text; DO NOT SEND ATTACHMENTS! ]
