Thanks for connecting the dots. I was missing the connection to the OS exec environment. Trying to use the "env" definitely won't be a good solution to my particular problem. The thousands of scripts I will be loading are variable sized and may vary quite a bit depending on how much data they contain. A lot of data structures have to be populated as the scripts are loaded. It looks to me like my only choice is to have each process perform the load. One other thought I have is to maybe have the master communication process load all the files and write out some sort of compilation file that all the child processes would load instead or re-executing the entire process.
On Friday, November 30, 2012 11:35:13 AM UTC-5, Ben Noordhuis wrote: > > On Fri, Nov 30, 2012 at 5:16 PM, spqr <[email protected] <javascript:>> > wrote: > > So, I guess this is a fairly stupid question because I can pass > everything > > to the process as part of the "env" > > Maybe a new question is that since I'm talking about "quite a lot of > junk," > > is there any negative consequence > > of passing a really large env to the child process. > > Not intrinsically but most (all?) operating systems put some arbitrary > upper limit on the environment size. On modern Linux, for example, > the maximum length of arguments + environment is usually (but not > always) 2 MB. > > In case of doubt, consult the limitations section of `man execve`. > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
