Re: problem when different users run the same pp-packed executable

On 9 Feb 2005 at 10:05, David Cho-Lerat wrote:

> 
> 
> Thank a lot for your help. It all makes more sense now.
> 
> I'm still a bit confused, though : I just packed a simple
> "hello World" program with pp, making sure first that
> the username I used (the so-called 'nanpla00' ..)
> did appear somewhere in an environment variable,
> so that the par-nanpla00 dir be created instead of par-SYSTEM.
> 
> Issuing the 'env' command (I'm using bash under Solaris 8) showed
> this variable (among others) :
> 
> LOGNAME=nanpla00
> 
> I then checked that Perl itself had access to it :
> 
> perl -e 'print "$ENV{LOGNAME}\n"'
> 
> returned, as expected :
> 
> nanpla00
> 
> So far so good, and yet, when I packed the app as so :
> 
> pp -o hello.exe hello.pl
> 
> it is indeed /tmp/par-SYSTEM that was created by pp and not
> /tmp/par-nanpla00 .. 
> I then deleted par-SYSTEM and ran the app, which recreated par-SYSTEM.
> 
> Shouldn't par-nanpla00 have been created when running pp or the app itself ?
> Isn't LOGNAME one of the environment variables used by PAR ?
> If not, which environment variable do you recommend I set to the correct 
> value ?
> 
> I tried the alternate solution of setting PAR_TEMP before running pp or the 
> app :
> 
> export PAR_TEMP=/tmp/mytest
> env
> 
> ...
> PAR_TEMP=/tmp/mytest
> ...
> 
> but it did not work : /tmp/par-SYSTEM was used again when running pp or the 
> app.
> I tried setting PAR_TEMP to just 'mytest', thinking that maybe the '/tmp/' 
> part was added
> by PAR, but it did not work either.
> 
> Is there anything special to do under Solaris to make this work ?
> What do you suggest I should do ?
> 

I dashed off my previous answer too quick. Sorry. After checking:

When constructing the temp dirname, PAR only looks for $ENV{USER} or 
$ENV{USERNAME} on 
non-Win32 systems. On Win32 it makes a Windows call to get the username.

Is LOGNAME the variable that is normally automatically set after logging into 
your 
Solaris, and neither of the other two are present? Perhaps we should add 
LOGNAME to 
PAR's search list.

The variable to override the username temp dir is PAR_GLOBAL_TEMP, not 
PAR_TEMP. There 
are three "global" variables that override the PAR app values: PAR_GLOBAL_TEMP, 
PAR_GLOBAL_CLEAN and PAR_GLOBAL_DEBUG.

While running, the PAR app sees PAR_TEMP, PAR_CLEAN and PAR_DEBUG set according 
to the 
PAR app internal values or the overridden value from the "global" value. They 
are 
called "global" because, once set, they affect all subsequent PAR apps.

Alan Stewart