--- Ted Stresen-Reuter wrote: > > I suspect it is due to the fact that the > line that deletes the report is rm $REPORT instead of rm -f $REPORT > (which overrides the "interactive" version of rm that asks if you > really want to delete something), but I'm not sure.
I am not sure either. How are you running the script? Typically when an account gets "interactive rm" it is because there is an alias set up for that account (alias rm="rm -i"). If you are running the script from a cronjob, you should attempt to make sure that cronjob's environment is not picking up login aliases, etc. One quick fix is to use "\rm" in the script instead of "rm" (that tells the shell to find the rm command and skip shell aliases or functions). A better way is to use "/bin/rm" directly. [In fact, thanks for pointing this out...I'm going to use full paths to my binaries in my script "RM_CMD=/bin/rm" "WC_CMD=/bin/wc", etc.] The -f flag won't hurt, but it shouldn't be necessary if you are running the script as the same user each time. > Also, I'm getting far too much information in my report: lines and > lines of what appear to be hex numbers. Any idea how to turn that off? Can you post a snippet of the output? Preferably with any lines just before the hex that seem to indicate what's causing the output. greg_fenton. ===== Greg Fenton [EMAIL PROTECTED] __________________________________________________ Do you Yahoo!? New DSL Internet Access from SBC & Yahoo! http://sbc.yahoo.com ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ htdig-general mailing list <[EMAIL PROTECTED]> To unsubscribe, send a message to <[EMAIL PROTECTED]> with a subject of unsubscribe FAQ: http://htdig.sourceforge.net/FAQ.html
