What does
xterm -fg green -bg black -e 'gpg Personal/data.ods.gpg;echo $?' tell you? I'm thinking
that gpg fails, so oocalc never launches (because you conditioned its execution with
'&&', and the script continues to shred the file.
My amd64 succeeds executing this (s/gpg/echo-to-tmpfile/). I would initially
assume it's the usage causing the issue, rather than some arch-dependent thing.
Amit
Mick wrote:
Hi All,
I have run into a problem which I cannot explain. I am trying to run this
script in a amd64 installation:
xterm -fg green -bg black -e 'gpg Personal/data.ods.gpg && oocalc \
Personal/data.ods; shred --remove -z -v DATA/data.ods'
On a x86 system, oocalc launches, I use the file and when I close it shred
removes it. On the amd64 system, the file is shredded as soon as it is
opened. This is what happens:
[snip ...]
gpg: AES256 encrypted data
gpg: original file name='data.ods'
random usage: poolsize=600 mixed=0 polls=0/0 added=0/0
outmix=0 getlvl1=0/0 getlvl2=0/0
secmem usage: 64/32768 bytes in 1 blocks
I18N: Operating system doesn't support locale "en_US"
shred: Personal/data.ods: pass 1/4 (random)...
shred: Personal/data.ods: pass 2/4 (random)...
shred: Personal/data.ods: pass 3/4 (random)...
shred: Personal/data.ods: pass 4/4 (000000)...
shred: Personal/data.ods: removing
shred: Personal/data.ods: renamed to Personal/00000000
shred: Personal/00000000: renamed to Personal/0000000
shred: Personal/0000000: renamed to Personal/000000
shred: Personal/000000: renamed to Personal/00000
shred: Personal/00000: renamed to Personal/0000
shred: Personal/0000: renamed to Personal/000
shred: Personal/000: renamed to Personal/00
shred: Personal/00: renamed to Personal/0
shred: Personal/data.ods: removed
Is this something 64bit specific? Shouldn't xrterm behave the same in both
x86 and amd64 with regards to this script? How do I get it to keep oocalc
open and shred to kick in only after the oocalc application is closed?
