diff options
author | Jim Meyering <jim@meyering.net> | 2001-05-11 11:23:37 +0000 |
---|---|---|
committer | Jim Meyering <jim@meyering.net> | 2001-05-11 11:23:37 +0000 |
commit | 5848516f26c9bde11cbbe12cf76bc8e9cd843d78 (patch) | |
tree | ffc59fa153baeaa04c7699f7d9407646705c2edc /doc | |
parent | a46bcc4636dd71c3eddb9e303c7b5dbf81928e23 (diff) | |
download | coreutils-5848516f26c9bde11cbbe12cf76bc8e9cd843d78.tar.xz |
(shred invocation): Warn about backups and mirrors.
Diffstat (limited to 'doc')
-rw-r--r-- | doc/omni-utils.texi | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/doc/omni-utils.texi b/doc/omni-utils.texi index 5950e4dcd..9b60b226e 100644 --- a/doc/omni-utils.texi +++ b/doc/omni-utils.texi @@ -6125,11 +6125,11 @@ not truncate or remove the output file. This default is more suitable for devices, which typically cannot be truncated and should not be removed. -Don't forget about the risk of backups. -In large multiuser environments, there may be long-term file system -backups that retain copies of files that are later shredded. While -it may be impossible to recover a shredded file from disk, it may be -relatively trivial to do so from backup media. +Finally, consider the risk of backups and mirrors. +File system backups and remote mirrors may contain copies of the +file that cannot be removed, and that will allow a shredded file +to be recovered later. So if you keep any data you may later want +to destroy using @code{shred}, be sure that it is not backed up or mirrored. @example shred [@var{option}]@dots{} @var{file}[@dots{}] |