Ok, in that case I'll refrain from posting the bugs so as not to
needlessly bother the mysql developers. I can work around the
problem(s)easily enough, anyway.
I'll make a couple of additions to the INSTRUCTIONS file with these
issues, so that people running 4.1 wanting to compile this don't have to
figure it out for themselves.
Another thing that came to mind yesterdaynight;
I know that its possible to get events from the NDB cluster. However,
as far as I know this is only in the form of a character string (in
4.1). Is it possible to read these events out in more detail (perhaps a
structure with information pertaining to the node(s) involved)? Or was
this added in 5.0/5.1?
I did not find the ndb_logevent_get_next() function as seen on the page
below (found using Google).
http://flake.defau.lt/docs/mgmapi/
Given this information, it might be possible to send out SNMP traps for
log events. That way you can see when for instance a disk node dies, or
perhaps when a backup is started / completed.
Cheers,
Michel
Stewart Smith wrote:
> On Wed, 2006-07-05 at 13:52 +0200, Michel Stam wrote:
>
>> http://bugs.mysql.com/bug.php?id=10185
>> Apparently is one of my errors. Looking at that, are bug reports
>> regarding the mgmapi even considered?
>>
>
> Would consider for 5.0 and 5.1, although probably not care about 4.1 (as
> it's not a critical problem and we tend to only fix critical crashing or
> incorrect result bugs in 4.1)
>
--
Michel Stam ing.
Software Development Engineer
michel@stripped <mailto:michel@stripped>
Houtweg 29
1251 CS Laren
The Netherlands
t: +31 (0)35 548 98 58
f: +31 (0)35 531 65 61
www.teleconcept.nl <http://www.teleconcept.nl>