From: Goldsack, P. <pat...@hp...> - 2004-06-23 12:19:33
|
Ashish, Since file logging will require some configuration data, such as defining the file name and location, it seems to me that expecting this to be configured as part of default.sf or some other description is the better option. As console logging is in essence configuration free, this makes it a better automatic default. Patrick -----Original Message----- From: sma...@li... [mailto:sma...@li...] On Behalf Of Ashish Awasthi Sent: 23 June 2004 12:43 To: sma...@li... Subject: [Smartfrog-developer] Framework logging. Hi folks, I propose to make file logging as default logging mechanism for the SmartFrog framework. Console logging does not helps much in production environment which would typically have several remote SF nodes. It is a necessity in the scenarios where we automatically install SF and start daemon in remote machines. Currently to enable file logging one has to edit default.sf, which is not feasible in automated SF installer. However we may continue to provide option of console logging in default.sf. We can also provide a command line option to enable and disable file logging while starting SF daemon. Let me know your thoughts. Thanks, Ashish ------------------------------------------------------- This SF.Net email sponsored by Black Hat Briefings & Training. Attend Black Hat Briefings & Training, Las Vegas July 24-29 - digital self defense, top technical experts, no vendor pitches, unmatched networking opportunities. Visit www.blackhat.com _______________________________________________ Smartfrog-developer mailing list Sma...@li... https://lists.sourceforge.net/lists/listinfo/smartfrog-developer |