Translations by Jun Kobayashi

invalid template, %s; with --tmpdir, it may not be absolute

failed to create directory via template %s

--strip-trailing-slashes remove any trailing slashes from each SOURCE argument -S, --suffix=SUFFIX override the usual backup suffix

Usage: %s [OPTION] [COMMAND [ARG]...]

cannot get niceness

cannot set niceness

line number overflow

invalid header numbering style: %s

invalid body numbering style: %s

invalid line numbering format: %s

Usage: %s COMMAND [ARG]... or: %s OPTION

Run COMMAND, ignoring hangup signals.

ignoring input

ignoring input and appending output to %s

ignoring input and redirecting stderr to stdout

failed to redirect standard error

invalid type string %s

invalid type string %s; this system doesn't provide a %lu-byte integral type

invalid type string %s; this system doesn't provide a %lu-byte floating point type

skip-bytes + read-bytes is too large

nonportable character %s in file name %s

empty file name

%s: unable to determine maximum file name length

limit %lu exceeded by length %lu of file name %s

limit %lu exceeded by length %lu of file name component %s

Usage: %s [OPTION]... [USER]...

no username specified; at least one must be specified when using -l

starting page number %<PRIuMAX> exceeds page count %<PRIuMAX>

Page %<PRIuMAX>

invalid field width: %s

invalid precision: %s

%.*s: invalid conversion specification

warning: ignoring excess arguments, starting with %s

invalid gap width: %s

failed to chdir to %s

failed to stat %s

couldn't find directory entry in %s with matching i-node

-f, --canonicalize canonicalize by following every symlink in every component of the given name recursively; all but the last component must exist -e, --canonicalize-existing canonicalize by following every symlink in every component of the given name recursively, all components must exist

--one-file-system when removing a hierarchy recursively, skip any directory that is on a file system different from that of the corresponding command line argument

Usage: %s CONTEXT COMMAND [args] or: %s [ -c ] [-u USER] [-r ROLE] [-t TYPE] [-l RANGE] COMMAND [args]

format string may not be specified when printing equal width strings

CAUTION: Note that shred relies on a very important assumption: that the file system overwrites data in place. This is the traditional way to do things, but many modern file system designs do not satisfy this assumption. The following are examples of file systems on which shred is not effective, or is not guaranteed to be effective in all file system modes:

* log-structured or journaled file systems, such as those supplied with AIX and Solaris (and JFS, ReiserFS, XFS, Ext3, etc.) * file systems that write redundant data and carry on even if some writes fail, such as RAID-based file systems * file systems that make snapshots, such as Network Appliance's NFS server

* file systems that cache in temporary locations, such as NFS version 3 clients * compressed file systems

In the case of ext3 file systems, the above disclaimer applies (and shred is thus of limited effectiveness) only in data=journal mode, which journals file data in addition to just metadata. In both the data=ordered (default) and data=writeback modes, shred works as usual. Ext3 journaling modes can be changed by adding the data=something option to the mount options for a particular file system in the /etc/fstab file, as documented in the mount man page (man mount).

In addition, 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.

%s: cannot rewind

%s: lseek failed

%s: file too large

%s: pass %lu/%lu (%s)...%s/%s %d%%