> Yesterday i lost a 2,3 GB big file because mkisofs "silently" skipped it. > > mkisofs ... $dir && rm -rf $dir > > I had the luck that i can reget that file. But next time it's possibel > that i'm not so lucky. So it would be best to "die" instead of a "silent" > warning that a file was skipped. (At least as a commandline-option. > Something like the "Make warnings to errors" from compilers (this can be > especially usefull for scripts where the warnings aren't seen (Today i saw > the warning because i was watching the process today)). Or a special > option "die when files are too big")
Now everything is right for my script. a "#include <unistd.h>" at the top and a "_exit(1);" after the "errormessage" and everything works flawlessly now and the script doesn't wipe a directory from which a BROKEN image was created from. Bis denn -- Real Programmers consider "what you see is what you get" to be just as bad a concept in Text Editors as it is in women. No, the Real Programmer wants a "you asked for it, you got it" text editor -- complicated, cryptic, powerful, unforgiving, dangerous. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
