Re: passing env{} variable to child fails on linux,works on windows

Hello sdetweil,

Since you are testing for MS and treating the problem different for *nix and MS, you may not know about '/dev/shm' which most modern *nix have. If you do a 'df' you'll see if it's there. What this does is allow you to share information between different processes in *nix. It treats memory as a separate filesystem for you to 'open/read/write/close' in memory files without going to disk.

In my testing, I've found it to be 2 or more times faster than using disk, and it's 'cleaned-up' on re-boot.

I don't think the method you're using in *nix will work, since there is no relationship between the process created with 'open' and your process. Why it works in MS, someone else will have to explain. If you use 'fork', all variables are copied to the new process, so you can say:

    our $test_switch = 1;      ##  I recommend using 'our' over 'my' i
+n this case
                               ##  It signals that it's something to b
+e shared
[download]

and it will be available in the new 'fork'ed process.

Good Luck!

"Well done is better than well said." - Benjamin Franklin

Comment on Re: passing env{} variable to child fails on linux,works on windows Download Code

Replies are listed 'Best First'.
Re^2: passing env{} variable to child fails on linux,works on windows by sdetweil (Sexton) on Jan 12, 2013 at 19:03 UTC
>since there is no relationship between the process created with 'open' and your process well, there it is then.. its not a 'child' its a peer.. never a dull moment.. thanks.. we have to think on the best way to do this..	[reply]
Re^3: passing env{} variable to child fails on linux,works on windows by dave_the_m (Monsignor) on Jan 12, 2013 at 19:37 UTC
well, there it is then.. its not a 'child' its a peer.. Flexvault is mistaken. It's a child, and it does inherit environment variables. Here are a couple of linux scripts that demonstrate this. First, /tmp/myenv just prints any environment variables that have 'MY' in the name: `#!/usr/bin/perl print "$_=>$ENV{$_}\n" for grep /MY/, sort keys %ENV;` [download] Then the main script, which 'opens' myenv: `#!/usr/bin/perl $ENV{MYA} = 'a'; $ENV{MYB} = 'b'; $ENV{C} = 'c'; open(CMD, "/tmp/myenv 2>&1 \|") or die "open: $!\n"; while (<CMD>) { chomp; print "got: <$_>\n"; }` [download] Running this gives: `got: <MYA=>a> got: <MYB=>b>` [download] Dave.	[reply] [d/l] [select]
Re^4: passing env{} variable to child fails on linux,works on windows by sdetweil (Sexton) on Jan 13, 2013 at 13:39 UTC
thank you. using your example I tested on my platform, and it worked. but my app didn't.. the difference was that I called $ENV{} from the thread code (&routine below), vs the main app code.. `threads->create(&routine);` [download] moving the $ENV{} to the main code allows it to work. `$ENV{'SKIP_SYSTEM'}='1'; threads->create(&routine);` [download]	[reply] [d/l] [select]
Re^5: passing env{} variable to child fails on linux,works on windows by andal (Hermit) on Jan 14, 2013 at 09:19 UTC
Re^5: passing env{} variable to child fails on linux,works on windows by thargas (Deacon) on Jan 14, 2013 at 13:49 UTC
Re^3: passing env{} variable to child fails on linux,works on windows by flexvault (Monsignor) on Jan 12, 2013 at 19:11 UTC
sdetweil, How about: `my @results = qx/script.plx -$envparm/;` [download] You get the results of the script in '@results' and you pass your script the required parameter that it needs. Maybe? Regards...Ed "Well done is better than well said." - Benjamin Franklin	[reply] [d/l]