From: Andreas U. <unt...@ma...> - 2005-11-21 15:18:47
|
I'm using the latest SmartFrog dist, 3.08.000 with logging to a file, i.e. in default.ini has: org.smartfrog.sfcore.logging.LogImpl.localLoggerClass=org.smartfrog.sfcore.logging.LogToFileImpl org.smartfrog.sfcore.logging.LogToFileImpl.showMethodCall=false org.smartfrog.sfcore.logging.LogToFileImpl.showDateTime=false org.smartfrog.sfcore.logging.LogToFileImpl.fileNamePrefix="smartfrog" org.smartfrog.sfcore.logging.LogToFileImpl.useHostNameInFileName=false org.smartfrog.sfcore.logging.LogToFileImpl.useProcessNameInFileName=false org.smartfrog.sfcore.logging.LogToFileImpl.path="/var/log" org.smartfrog.sfcore.logging.LogToFileImpl.useDatedFileName=false Now I notice that this causes a separate log file for every component I deploy into the system. Furthermore the filenames have a whitspace which make them difficult to view on Linux: smartfrog_HOST hostname.mydomain.org_rootProcess_sfDefault.sf.log smartfrog_HOST hostname.mydomain.org_rootProcess.sf.log smartfrog_HOST hostname.mydomain.org_rootProcess_torqueClientInstall_myShell.sf.log smartfrog_HOST hostname.mydomain.org_rootProcess_torqueClientInstall.sf.log smartfrog_SFCORE_LOG.sf.log smartfrog_.sf.log I have two questions: 1. I would like to have just one log file. How can I force everything to be logged just into one file /var/log/smartfrog.log ? 2. If 1 is not possible, how can I force SF to not use whitespaces in the filenames ? Thanks, Andreas -- http://cern.ch/openlab |