Joe Wells <[EMAIL PROTECTED]> writes: > Kai Antweiler <[EMAIL PROTECTED]> writes: > >> I've got an idea what you can try: >> # cd .glob2/logs >> # for in * ; do rm $i; touch $i; chmod -w $i ;done >> >> This should work without changes to the glob2 source code. > > I'll try this last option (denying write permission on the .log files) > and see if it works. (I'm not planning on compiling from CVS any time > in the near future. I'm happy to try releases.)
Okay, I've tried this. It doesn't work, because glob2 just renames the .log files to .log~ and creates new ones. It does work to remove write permission on the ~/.glob2/logs directory. If I do this, then glob2 stops making log files and instead spews all of that data to stdout. It is enough to redirect stdout (not stderr) to /dev/null to get rid of this. -- Joe _______________________________________________ glob2-devel mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/glob2-devel
