1 .\" DO NOT MODIFY THIS FILE! It was generated by help2man 1.35.
2 .\"*******************************************************************
4 .\" This file was generated with po4a. Translate the source file.
6 .\"*******************************************************************
7 .TH SHRED 1 "April 2010" "GNU coreutils 8.5" ユーザーコマンド
9 shred \- overwrite a file to hide its contents, and optionally delete it
11 \fBshred\fP [\fIOPTION\fP]... \fIFILE\fP...
13 .\" Add any additional description here
15 Overwrite the specified FILE(s) repeatedly, in order to make it harder for
16 even very expensive hardware probing to recover the data.
18 Mandatory arguments to long options are mandatory for short options too.
20 \fB\-f\fP, \fB\-\-force\fP
21 change permissions to allow writing if necessary
23 \fB\-n\fP, \fB\-\-iterations\fP=\fIN\fP
24 overwrite N times instead of the default (3)
26 \fB\-\-random\-source\fP=\fIFILE\fP
27 get random bytes from FILE
29 \fB\-s\fP, \fB\-\-size\fP=\fIN\fP
30 shred this many bytes (suffixes like K, M, G accepted)
32 \fB\-u\fP, \fB\-\-remove\fP
33 truncate and remove file after overwriting
35 \fB\-v\fP, \fB\-\-verbose\fP
38 \fB\-x\fP, \fB\-\-exact\fP
39 do not round file sizes up to the next full block;
41 this is the default for non\-regular files
43 \fB\-z\fP, \fB\-\-zero\fP
44 add a final overwrite with zeros to hide shredding
52 If FILE is \-, shred standard output.
54 Delete FILE(s) if \fB\-\-remove\fP (\fB\-u\fP) is specified. The default is not to
55 remove the files because it is common to operate on device files like
56 /dev/hda, and those files usually should not be removed. When operating on
57 regular files, most people use the \fB\-\-remove\fP option.
59 CAUTION: Note that shred relies on a very important assumption: that the
60 file system overwrites data in place. This is the traditional way to do
61 things, but many modern file system designs do not satisfy this assumption.
62 The following are examples of file systems on which shred is not effective,
63 or is not guaranteed to be effective in all file system modes:
65 * log\-structured or journaled file systems, such as those supplied with AIX
66 and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.)
68 * file systems that write redundant data and carry on even if some writes
69 fail, such as RAID\-based file systems
71 * file systems that make snapshots, such as Network Appliance's NFS server
73 * file systems that cache in temporary locations, such as NFS version 3
76 * compressed file systems
78 In the case of ext3 file systems, the above disclaimer applies (and shred is
79 thus of limited effectiveness) only in data=journal mode, which journals
80 file data in addition to just metadata. In both the data=ordered (default)
81 and data=writeback modes, shred works as usual. Ext3 journaling modes can
82 be changed by adding the data=something option to the mount options for a
83 particular file system in the /etc/fstab file, as documented in the mount
86 In addition, file system backups and remote mirrors may contain copies of
87 the file that cannot be removed, and that will allow a shredded file to be
92 shred のバグは bug\-coreutils@gnu.org に報告してください。
94 GNU coreutils のホームページは <http://www.gnu.org/software/coreutils/> です。
96 GNU ソフトウェアを使用するための一般的なヘルプ <http://www.gnu.org/gethelp/> にある。
98 shred の翻訳のバグは <http://translationproject.org/team/> に報告してください。
100 Copyright \(co 2010 Free Software Foundation, Inc. License GPLv3+: GNU GPL
101 version 3 or later <http://gnu.org/licenses/gpl.html>.
103 This is free software: you are free to change and redistribute it. There is
104 NO WARRANTY, to the extent permitted by law.
106 \fBshred\fP の完全なマニュアルは Texinfo マニュアルとして用意されている。
107 \fBinfo\fP と \fBshred\fP のプログラムがお使いの環境に適切にインストールされているならば、
110 \fBinfo coreutils \(aqshred invocation\(aq\fP
112 を実行すると、完全なマニュアルを読むことができるはずである。