I agree what you are saying. see my post at http://forum.mysqlperformanceblog.com/s/t/763/
it does indicate that error log is even version sensitive. Whatever error log or error db are fine to user as long as we newbies don't stuck with the errors without solutions. On 5/27/08, Javier Barroso <[EMAIL PROTECTED]> wrote: > > > > On Mon, May 26, 2008 at 8:00 AM, Debian Linux <[EMAIL PROTECTED]> > wrote: > >> Similar to the ones in the following >> >> >> http://service1.symantec.com/SUPPORT/powerquest.nsf/31c3099514a5cd2788256e97004c7b22/082f16ef9cb0572f88256e75007cae52?OpenDocument >> >> http://msdn.microsoft.com/en-us/library/ms681386(VS.85).aspx<http://msdn.microsoft.com/en-us/library/ms681386%28VS.85%29.aspx> >> >> From my understanding is that MS OS backbone errors are standardised >> coding but the solution varies from one application client to another. >> > > I think it should be a good idea to create a site (¿wiki?) where you could > find possible solutions to a determined log error pattern. I don't think > bugs.debian.org is like that. "Debian Linux" user refers to a > documentation like oracle use. > > The problem is how to sort the possible log errors, and how to bind the log > errors to specifics versions of packages. > > So I think should be better to create a file like the FAQs in every > package/program where the autor/or contributors write the possible message > logs errors and their explication. It could be named "FLE" (Frequently Logs > Errors) or FLEW if warning messages are incluyed. > > I know the best method is read and understand manuals and then the message > logs are sufficient to resolv the problem (but sometimes it take more time > that you have) > > What do you think about it ? > > Sorry for my english >
