Am 14.07.2010 um 11:57 schrieb Pavel Sanda: > Stephan Witt wrote: >> One remark here (nitpick): >> In the first example "cat" is not the program which overwrites the original. >> It is the shell - and to avoid that stupid mistake they introduced the >> variable noclobber. >> When it is set and if your scripts assume overwrite of already existent >> files is ok they fail - out of the blue! > > your example would be appropriate if noclobber is set out of the blue by > default in my distribution and all bash > scripts around the world which suppose ">" overwrite stop to work. the would > be big fun and i hear the scream ;)
Yes. I made this experience long ago. Not that the distribution had this default... the sysadmin wanted to be helpful and protect the users :-) So the noclobber was set before the start of any user script globally. So I had to "fix" my scripts... :( Anyway, I have no strong opinion here. And I can follow both sides... Stephan
