From the case: https://sourceforge.net/tracker/?func=detail&atid=875350&aid=3440417&group_id=175965
Status: Closed Resolution: Wont Fix Sender: einhverfr The error occurs as a part of the routines for detecting database versions.Because this is a rare task and this enables better debugging, I would be in favor of fixing it as a low priority issue when a replacement is agreed upon. ===================================================================== Thanks for an explanation of the error. But, could we do this a little better ? (I hope am not the first new user that read logs, and post error's) I suggest that before the "routines for detecting database versions" start we put out a log line with a general info about the errors that follows. When the "routines for detecting database versions" ends - we send out a new log line that informs about the end of the test. I suggest: Resolution: Wont Fix change to Resolution: Postponed ------------------------------------------------------------------------------ All the data continuously generated in your IT infrastructure contains a definitive record of customers, application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-novd2d _______________________________________________ Ledger-smb-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/ledger-smb-devel
