Hello,

Thanks for a very useful module.

I prefer to set PAR_GLOBAL_TEMP in /etc/environment file on linux.

I've come up with the following code I would like to contribute to achieve
this.
I suspect this code is probably best placed quite early in sub
_par_init_env:

BEGIN{
  my $envfile="/etc/environment";
  if (-r $envfile)
  {
    open(my $fh,"<",$envfile)or die $!;
    while(<$fh>)
    {
      my $line=$_;
      $line=~s/^\s+|\s+$//g;      my @ea=split("=",$line);
      if((scalar @ea == 2)and($ea[1]=~m/^[\S]+$/))
      {
        $ENV{$ea[0]}=$ea[1];
      }
    }
  }
}


I find cron jobs, systemd services and other executables
that call PAR EXEs' don't always have the correct environment set.
This causes PAR to then attempt to unpack in /tmp/ when they should
unpack elsewhere as set in PAR_GLOBAL_TEMP in /etc/environment.

The attempt to unpack fails if /tmp/ is mounted noexec, which I'm finding
is being used more often these days.


Thanks,
Robin Twiggs

Reply via email to