gpg: failed to create temporary file

[Joseph Oreste Bruni]

One last test: Rather than having BPEL run "gpg" directly, perhaps you could have it run a shell script that in turn runs "gpg". You should then be able to set whatever variables you need prior to the call of gpg from within the shell script. You can also enable tracing (set -o xtrace) to help with script debugging.

Joe



On Monday, February 09, 2009, at 01:40PM, <lee_andre at bellsouth.net> wrote:
>Okay I decided to take a different route.
>I decided to create a directory and put the files from ~/.gnupg to /opt/oracle/gpgfiles, my admin edited the .bash_profile to have GNUPGHOME = /opt/oracle/gpgfiles.  When I run my process I still get  gpg: failed to create temporary file `~/.gnupg/.#lk0x552ac57230.tst-dataexch.30375': No such file or directory gpg: fatal: ~/.gnupg: can't create directory: No such file or directory secmem usage: 0/0 bytes in 0/0 blocks of pool 0/32768.
>
>This leads me to believe GNUPGHOME is not setting the path to look into this directory.  Not sure what else I'm missing.
>
>Any suggestions???  I'm wide open.
>-------------- Original message from Joseph Oreste Bruni <jbruni at me.com>: -------------- 
>
>
>> Hi Lee, 
>> 
>> I'm at a complete loss of what else could be the problem. Sorry. 
>> 
>> Joe 
>> 
>> 
>> On Friday, February 06, 2009, at 08:17AM, wrote: 
>> >oh sorry my linux admin informed me what is SE Linux. 
>> >We dont have SE running on our servers >-------------- Original message from Joseph Oreste Bruni : 
>> -------------- 
>> > 
>> > 
>> >> How about the SE Linux setting? SE Linux, when enabled, activates 
>> >> mandatory access controls that go beyond the traditional owner/group/ 
>> >> other Unix permissions. It has bitten me before. 
>> >> 
>> >> 
>> >> On Feb 5, 2009, at 3:12 PM, lee_andre at bellsouth.net wrote: 
>> >> 
>> >> > My linux admin added $HOME in the bash_profile and fix the $PATH and 
>> >> > still receive the same problem. 
>> >> > Also I ran my utility in the DEV environment and the result were the 
>> >> > read out as in my TEST env, but yet the DEV env works >> > -------------- Original message from Joseph Oreste Bruni > > >: 
>> -------------- 
>> >> > 
>> >> 
>> > 
>