corrupt trustdb caused by commandline?
Atom Smasher
atom at smasher.org
Thu May 25 06:15:40 CEST 2006
On Thu, 25 May 2006, David Shaw wrote:
>> * why was closing stdout causing gpg to have problems?
>
> It's not a GPG thing, specifically. Closing stdout (or stderr) is
> actually a pretty dangerous thing to do on *any* program that opens
> files and also uses printf.
...
> If the goal is to squish stdout, you should redirect stdout to
> /dev/null rather than closing it outright.
>
>> * will this patch be incorporated into production?
>
> Yes. Already has, actually.
==========================
this is being used in part of a script that just tests for return status,
and any output is undesired. would you recommend changing the script to
redirect stdout/stderr to /dev/null? or should it be ok, now, to just
close stdout/stderr? or is there a better way altogether that i'm
overlooking?
thanks...
--
...atom
________________________
http://atom.smasher.org/
762A 3B98 A3C3 96C9 C6B7 582A B88D 52E4 D9F5 7808
-------------------------------------------------
"A farmer's duty, is protecting the earth, maintaining
it's fertility, and maintaining the fertility of seed.
That is part of being a farmer. A farmer is not a
low-paid tractor driver, that's a modern definition of
what a farmer is. The real definition of a farmer is a
person who relates to the land and relates to the seed
and keeps it for future generations, keeps renewing
it, fertility."
-- Dr. Vandana Shiva
More information about the Gnupg-devel
mailing list