Hi, and thank you very much for your response. I found the PAR_TEMP variable referenced in the PAR::Environment module. In the ende playing with the file who_am_i.txt here yelded a lot. If I see it right, I should make a copy of my executable without -gui argument to see the command line and with a debug print of $ENV{PAR_TEMP} as an addition. Could then $ENV{PAR_GLOBAL_TEMP} be set in the script to change the location? In the above document the variable is set outside the programm.
Another question: how (in a nutshell) to benchmark the packed executable with simulation of several users. I did use the calls of subroutines with the Benchmark module. Should it be system calls to the executable in this case? However then I just start many instances of the programm as one user, not as several different users, does it make difference? Another thing - this is a GUI application, it would then open each time? Do you mean, just putting exit at the end of the script would be useful?
Sorry for so many questions. I put some in the other replies too since you would not see me reply as Anonymous Monk :-).
In reply to Re^2: Simultaneous access to the tk script (details pitfalls)
by Anonymous Monk
in thread Simultaneous access to the tk script
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |