False insecure memory warnings...

[Joseph Bruni]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

David,

You bring up an excellent point here that can be generalized. 
Basically, in any automated task, it's probably a good idea to fully 
qualify the paths of any executable. Merely changing the system default 
configuration of the PATH variable can subtly alter a system if more 
than one copy of a program exist. By fully qualifying the path to the 
intended executable, you prevent such future problems.

Joe Bruni


On Thursday, April 3, 2003, at 02:40 PM, David Shaw wrote:

 >I've seen this a few times before.  Check to make sure that there
 >isn't another copy of gpg somewhere, and the gpg that cron is running
 >is the same one that you're running from the shell.
 >
 >David

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)

iEYEARECAAYFAj6M9moACgkQ4rg/mXNDweNlzQCg3m8juhBIWIvAe6QG5LQtIlJX
fywAn3e3ZEW0PxGMHCPMS440iE081Awy
=0qXc
-----END PGP SIGNATURE-----