False insecure memory warnings...
Fri Apr 4 05:04:02 2003
-----BEGIN PGP SIGNED MESSAGE-----
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.
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.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (Darwin)
-----END PGP SIGNATURE-----