in reply to Passing command line variables and PID's between processes

I know this doesn't address your original question but is there a reason you aren't calling system like this... system ($RUN_PROC2, @ARGV); Just asking. Now, if I understand, you 2 questions


I don't think that your arguments will get toasted by system. If system did something like $_[5]='blown away'; you'd be screwed but, without checking, I'm pretty confident it operates on copies of your variables, not directly on @_.

As for the second question check out pipes rather than shared memory for IPC. Not that my opinion matters much but I thinks pipes are easier to deal with and more stable than shared memory.

"So... What do all these little arrows mean?"
~unknown

Replies are listed 'Best First'.
Re: Re: Passing command line variables and PID's between processes
by mndoci (Scribe) on May 30, 2001 at 03:20 UTC
    Hi. Only reason I did not use @ARGV (which I am using now) is that I inherited these scripts and stuck to the original call. No $RUN_NAME is not changing between calls. There is only one weird error I am getting now and that seems to be related to the PID if anything at all.

    Thanks for your reply
    mndoci

    "What you do in this world is a matter of no consequence. The question is, what can you make people believe that you have done?"-Sherlock Holmes in 'A study in scarlet'