set -o noclobber command turn the option on (default it s off ) .
You can still append information but not overwrite the file .to turn it back off use : $ set +o noclobber .
I use it because i overwrite a file by accident , after thought , content of the file was very important , creating a one more file mean nothing for my hard disk (we are not anymore on the 64 k memory time) , but content of file is far much important . What we call exeprience :(
gnu@robby:/tmp$ set -o noclobber gnu@robby:/tmp$ cat tesk dffd gnu@robby:/tmp$ cat > tesk bash: tesk : impossible d'?craser le fichier existant gnu@robby:/tmp$ cat tesk dffd gnu@robby:/tmp$ cat >> tesk fdf gnu@robby:/tmp$ cat tesk dffd fdf gnu@robby:/tmp$
Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?
You must be signed in to comment.
commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.
Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.
» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10
Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):
Subscribe to the feed for:
some output >| protected_file