I am in a bit of a strange situation that ����m not quite sure how to solve.
- We run CAS 3.3.1 in our formal servers under Windows on jBoss. In those servers we place jBoss on the D: drive and run it as a Windows service. - In our developers workstations we usually run in Tomcat, and sometimes on jBoss for thorough testing. In these boxes the servers are started manually, and the whole thing is in the C: drive. One of the things we noticed was that if we use the default CAS log4.properties and launch it from a service, cas.log ends up in C:/Windows/System3���� a horrible place for i����� especially since it is our policy to put nothing but stock Windows in the C: drive of our formal servers. So, we modified C����� log4j.properties and set the location of the CAS log file to d:/jBoss/logs/cas.log. That forces the log file to the D: drive (most critical), and puts it in a better location. Bu���� that now causes an error in the developers boxes since they have no D: drive. Is there a good solution for this situation? If we removed CA���� log4j.properties from the application, will CAS be smart enough to automatically default to the serv�����s log4j configuration instead of expecting its own? Thanks, bruno -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
