ryan@aladdin.uucp (Ryan Waldron) (02/24/90)
When Configure asks how many aliases to include, why does try to limit this number to the 50-1000 range? Is there any reason (other than speed) that a number higher than this should not work? There are some users at my site who have an aliases.text that will require significantly more than 1000 available aliases to handle properly. Any caveats? -- Ryan Waldron @ Intergraph | "With glory and passion, aladdin!ryan@INGR.COM | no longer in fashion, ...!uunet!ingr!aladdin!ryan | the hero breaks his blade." - Kansas
syd@DSI.COM (Syd Weinstein) (02/24/90)
ryan@aladdin.uucp (Ryan Waldron) writes:
:When Configure asks how many aliases to include, why does try to limit this
:number to the 50-1000 range? Is there any reason (other than speed) that a
:number higher than this should not work? There are some users at my site
:who have an aliases.text that will require significantly more than 1000
:available aliases to handle properly. Any caveats?
Yes, Elm keeps the entire alias index table in memory. If the table is
large, it takes a lot of ram. Plus it must be searched each time.
Remember everyone has the same size alias table, its not dynamic.
(Maybe it should be, but no one has decided to deal with that problem).
Also remember that Elm, and many of its tools share the alias table,
they would all need to be changed.
--
=====================================================================
Sydney S. Weinstein, CDP, CCP Elm Coordinator
Datacomp Systems, Inc. Voice: (215) 947-9900
syd@DSI.COM or {bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235ryan@aladdin.uucp (Ryan Waldron) (02/27/90)
In article <1990Feb24.152425.1235@DSI.COM> syd@DSI.COM writes: >ryan@aladdin.uucp (Ryan Waldron) writes: >:When Configure asks how many aliases to include, why does try to limit this >:number to the 50-1000 range? Is there any reason (other than speed) that a > [...] >Remember everyone has the same size alias table, its not dynamic. >(Maybe it should be, but no one has decided to deal with that problem). What I want to know is whether or not something is going to "break" if I change MAX_SALIASES and MAX_UALIASES in config.h to something greater than 1024 (the value I am compiling with currently). I know that it will take more memory and be slower, and all that, but will it work properly? -- Ryan Waldron @ Intergraph | "With glory and passion, aladdin!ryan@INGR.COM | no longer in fashion, ...!uunet!ingr!aladdin!ryan | the hero breaks his blade." - Kansas
syd@DSI.COM (Syd Weinstein) (02/28/90)
ryan@aladdin.uucp (Ryan Waldron) writes: > What I want to know is whether or not something is going to "break" if I > change MAX_SALIASES and MAX_UALIASES in config.h to something greater than > 1024 (the value I am compiling with currently). I know that it will take > more memory and be slower, and all that, but will it work properly? There is no inherent limit of 1024, and no reason it won't work, in fact the configure will let you override it to that value if you tell it to. Its all memory and speed at this point. Therefore, bugs not withstanding, it should work just fine. -- ===================================================================== Sydney S. Weinstein, CDP, CCP Elm Coordinator Datacomp Systems, Inc. Voice: (215) 947-9900 syd@DSI.COM or {bpa,vu-vlsi}!dsinc!syd FAX: (215) 938-0235