why is an existing file not overwritten by output-file?

David T-G davidtg-gnupg@justpickone.org
Wed Jun 5 15:01:02 2002

Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Andreas --

=2E..and then akorthaus@web.de said...
% Hallo!
% Is there another possibility instead of:
% rm output.gpg | mysqldump database | gpg -o
% output.gpg -e --default-recipient andreas

This will never work; you're trying to pipe rm through everything else,
and I expect that mysqldump will not like having input sent to it.  You
want a semicolon instead of that first pipe.

As you have seen otherwise, though, you simply need to either tell gpg to
overwrite the file (--yes) or call it as a pipeline and overwrite the
file yourself (>file), assuming you then don't have any special noclobber
options of any sort that make the shell stand up and not step on, or
clobber, existing files.


David T-G                      * It's easier to fight for one's principles
(play) davidtg@justpickone.org * than to live up to them. -- fortune cookie
(work) davidtgwork@justpickone.org
http://www.justpickone.org/davidtg/    Shpx gur Pbzzhavpngvbaf Qrprapl Npg!

Content-Type: application/pgp-signature
Content-Disposition: inline

Version: GnuPG v1.0.7 (GNU/Linux)