Kevin, Depending on your version of CAS, there is a log4j properties file typically under the /WEB-INF/classes/log4j.properties directory of your CAS deployment. There you should see something like so: https://www.ja-sig.org/svn/cas3/tags/cas-3-2-1-final/cas-server-webapp/src/m ain/webapp/WEB-INF/classes/log4j.properties
You will want to remove the ³stdout² appender from ³log4j.rootLogger=ERROR, stdout, logfile². This line basically tells log4j to use the stdout appender, which is declared as a ConsoleAppender, and the logfile appender, which goes to a rolling file appender, to send log messages to. By sending messages to stdout, they go onto Tomcat¹s log and thus end up in catalina.log. HTH, Andrew On 10/6/08 7:00 AM, "Kevin S" <[EMAIL PROTECTED]> wrote: > Hi, > > INFO log entries are getting logged to catalina.out as well as cas.log. I know > I'm missing basic log4j info, but have looked and would appreciate a push in > the right direction. > > So, can someone explain or point me somewhere that explains how I can stop the > INFO entries from appearing in catalina.out? > I'm running CAS under Tomcat 5.5, and pretty much using the default log4j > logging. > > Thanks, > Kevin > > > _______________________________________________ > Yale CAS mailing list > [email protected] > http://tp.its.yale.edu/mailman/listinfo/cas -- Andrew R. Feller, Analyst Information Technology Services 200 Fred Frey Building Louisiana State University Baton Rouge, LA 70803 (225) 578-3737 (Office) (225) 578-6400 (Fax)
_______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
