On Sun, 09.12.07, Stephen Birch <[EMAIL PROTECTED]> wrote: > Nico Golde([EMAIL PROTECTED])@2007-12-09 21:18: > > > Cant the log files just be placed in the current working directory? > > > Either way, it sounds good. > > > > That would be the same problem if you call vobcopy in a > > world-writable directory. Checking if the file already > > exists and creating a unique name using mkstemp or opening the > > file with O_EXCL should be enough.
>From my short read of the man pages I got the impression that O_EXCL was not a posix feature. If so, it would limit vobcopy from running on not-posix conformant platforms (whatever they may be...) > > Of course its also an > > option to place them in the users home directory. > > Kind regards > > Point taken. Let me ask this, is there any real value in either -q or > -v -v opening a log file at all? Does it serve any useful purpose > since it is so easy to redirect stderr from the command line. > > Perhaps the simple solution is just to remove these features from > vobcopy? Bad idea, especially with -q. Vobcopy let's you redirect the output to stdout, in order to pipe it to e.g. mplayer or bbtools. It would be kind of bad if the progress bar also ended up in mplayer, don't you think :) And -v -v is there for the convenience of the bug-reporter. I got emails from people that simply said "your program told me to send you this, here you go". I doubt that they could have redirected stdout or err... > Robos ... what do you think? Loosing those options is not possible IMHO. Cheers Robos > Steve > > -- Robos - gpg --recv-keys --keyserver blackhole.pca.dfn.de 6EEADA09 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
