stupid sqlnet.log question

Sorry for what may seem like a stupid question, but is there a way to automatically truncate the sqlnet.log file on Win NT? I'm in development, and we have a separate prod group that is supposed to take care of our prod servers. Some of my clients were having issues connecting yesterday to production. I went to check the sqlnet.log file on prod for more details and found the file to be over 800MB (unacceptable). Obviously, I could not even open the file!

The prod group was remiss in truncating the log (even after my request) for me so I had to *fly* in the dark to resolve the connection issue.

Any ideas?

Thanks,

     Hannah

Unfortunaley, even though I am in development, I am responsible for supporting our users on production issues, however do not have enogh access tot he production environment to truly be able to help ARGH! Received on Fri Dec 08 2000 - 06:41:55 CST