Well... I thought Jeff's reply was very much to-the-point
but not harsh. Most importantly, it was informative.
That said, I do have some trouble with the notion of posting
the same question in multiple forums concurrently. A lot of
people will read your question and put some energy into
thinking about it, if not replying. If you already know you
are likely to get a better/faster reply elsewhere, then
in my opinion you are being inconsiderate of their time.
-- Rod
On Tuesday 15 June 2004 11:29 am, Matthew Lange wrote:
> Because one never knows how long it will be before one gets a reply, I
> sometimes post to newsgroups like this one, while simultaneously posting
> to tech-specific lists, and at the same time searching newsgoups/Google
> for a solution.
>
> I hope that the next time I do this on this list, that I will not
> receive such a harsh response as the one below.
>
> As long as solutions (or where they can be found) are published, we all
> benefit...sometimes inadvertantly. Much of the knowledge I have gained
> has been from monitorring list threads that I have returned to at a
> later date, when I actually need the info.
>
> It would be a sad day indeed if someone were not to post, because they
> were afraid of being ridiculed, belittled, demeaned, or otherwise told
> to go somewhere else.
>
> I hope that ketralnis@softhome.net doesn't think that the answer below
> reflects the general sentiment of people on this list--surely, it is not
> mine.
>
> My 2 cents.
>
> matthew
>
>
> Matthew Lange
> email: infosophist@infosoph.com
>
>
>
> -----Original Message-----
> From: vox-tech-bounces@lists.lugod.org
> [mailto:vox-tech-bounces@lists.lugod.org] On Behalf Of Jeff Newmiller
> Sent: Tuesday, June 15, 2004 9:02 AM
> To: lugod's technical discussion forum
> Subject: Re: [vox-tech] mysql experts?
>
> On Mon, 14 Jun 2004 ketralnis@softhome.net wrote:
>
> > This is a FreeBSD system, but it's standard MySQL (mysql Ver 12.22
> Distrib
> > 4.0.20, for portbld-freebsd5.0 (i386)).
>
> [... details omitted ...]
>
> > Does anyone know what could cause this? It looks to be, for whatever
> reason
> > writing out status information. But why it would do that, and why it
> would
> > take 30% CPU idling is beyong me. Any ideas?
>
> Someone here may have ideas... but you don't seem to have pursued the
> logically appropriate avenues for getting help. In this forum, this
> question is a head scratcher... in the correct forum, this is probably a
> FAQ. I, knowing nothing about it, googled "innodb monitor output" and
> immediately found the innodb manual page that describes the feature that
> generates this output. I suggest you read that, and if dropping the
> magic
> table doesn't fix it, ask in the mysql mailing list for more help.
>
> Yes, readers around here often answer diverse questions... but when
> there
> are obviously more appropriate places to get answers, please explain
> that
> you tried them and why they didn't work when posting here.
>
> ------------------------------------------------------------------------
> ---
> Jeff Newmiller The ..... ..... Go
> Live...
> DCN:<jdnewmil@dcn.davis.ca.us> Basics: ##.#. ##.#. Live
> Go...
> Live: OO#.. Dead: OO#.. Playing
> Research Engineer (Solar/Batteries O.O#. #.O#. with
> /Software/Embedded Controllers) .OO#. .OO#.
> rocks...2k
> ------------------------------------------------------------------------
_______________________________________________
vox-tech mailing list
vox-tech@lists.lugod.org
http://lists.lugod.org/mailman/listinfo/vox-tech