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

Ok, I checked the environment of different users, and
they only have LOGNAME set to their username.

For some reason, though, it is not so for the
superuser, who has both LOGNAME and
USER set :
..
LOGNAME=root
...
USER=root
...

I  suspect some kind of mis-configuration from the
sysadmins and not a standard Solaris behaviour,
but anyway I can arrange for all users to have their
USER and USERNAME variables set to whatever
value LOGNAME contains and I should be ok.
Besides, "export PAR_GLOBAL_TEMP=/tmp/mytest"
did work as expected.

In conclusion, I guess you could add LOGNAME
to PAR's search list but my feeling is that USER
should be set for everyone, and I'm going to see
to that now ;)

Thanks a lot for your help, I think I won't bother
you anymore now (for a while) ;)

(Thanks to the.noonings too !)

cheers,

David.




Alan Stewart a écrit :

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

  

--

____________________________________________

David Cho-Lerat

Chef de projets R&D

Asterion

ZI Nantes-Carquefou

Impasse de la Hache - CP 5911

44477 Carquefou cedex

téléphone     02 40 30 08 00 poste 310

fax                   02 40 30 03 36

e-mail         david.lerat@xxxxxxxxxxx, cellule.rd@xxxxxxxxxxx

site web       www.asterion.fr

 

signature.asc
Description: OpenPGP digital signature