Have you ever destroyed a file accidentally? If you set the noclobber C shell variable, or the noclobber option in bash and ksh, it can help you avoid these mistakes. Setting noclobber prevents you from destroying a file when you are .
Consider the following situation:
The command above destroys the old outputfile and creates a new
one. If you have misspelled the name of your output file, or if you
have forgotten that the file already exists and contains important
data, or (most common) if you really meant to type
>> instead of
(i.e., if you really meant to append to the end of outputfile,
rather than start a new one), tough luck; your old data is gone.
Setting the variable noclobber prevents this problem. If
noclobber exists, the C shell will not allow I/O redirection to
destroy an existing file, unless you explicitly tell it to by adding an
exclamation point (
!) after the C shell redirect symbol - or a
vertical bar (
|) in ksh and bash.
Here are examples.
The left column shows csh and tcsh;
the right column is for bash (ksh is similar):
set -o noclobber%
lsfilea fileb filea fileb %
anyprogram > fileb$
anyprogram > filebfileb: File exists. bash: fileb: Cannot clobber existing file %
anyprogram >! fileb$
anyprogram >| fileb% $
Be sure to put space after the
If you don't, the C shell thinks you're making a history reference and it
(usually) prints an error like
fileb: Event not found.
Remember that noclobber is not an environment variable, so any new shells you create. Therefore, if you want this feature, put the set command (above) in your shell's .
NOTE: In some C shells, noclobber will prevent you from redirecting standard output toor to a terminal unless you add the
The C shell noclobber variable has one other feature that's worth noting. Normally, the C shell lets you append to a file that doesn't exist. If noclobber is set under csh and tcsh, it won't; you can only append to files that already exist unless you use an exclamation point:
lsfilea fileb %
>> filecfilec: No such file or directory %