Chris, Moved this to the user list instead of the dev group. Hmmm strangely enough, I tried this on a CentOS system, I believe it forced me to be root over the tomcat user. I can re-check that shortly. I know it recreates the file <catalina.out> next time without any discourse, if I run the startup script as the tomcat user.
:: update :: I figured out WHY it forced me to be root. Someone *(may or may not have been me) ran the /etc/init.d/tomcat start script as the root user, not as the tomcat user which I believe would cause this behavior. - Josh On Sat, Nov 17, 2012 at 8:13 PM, Christopher Schultz < ch...@christopherschultz.net> wrote: > Josh, > > On 11/15/12 2:45 PM, Josh Gooding wrote: > > That is the tomcat default log file. Nothing server wise will happen if > > you delete if that is your concern. It just removes that particular log > > file. I believe that you have to either be root and/or have the server > > stopped to remove the file however. > > On a *NIX system, neither of the above statements are true: you may > delete the file while a process holds a file handle to the file (the > file will no longer be accessible to any other process -- at least under > its old name) without harm. > > I'm not sure what will happen on win32. You'll either fail to delete the > file or get the *NIX-style behavior. > > Once deleted, the file will be re-created when Tomcat next launches, as > long as the Tomcat process has "create" privileges for the > CATALINA_BASE/logs directory. > > -chris > >
