> LICENSE: LGPL
>
> This library is free software; you can redistribute it and/or
> modify it under the terms of the GNU Lesser General Public
> License (LGPL) as published by the Free Software Foundation; either
> version 2.1 of the License, or (at your option) any later version.

fixes the problem, but it worked in my elabinelab, so lets try it.

Fixed up vlan listing function under (apparently) new variable scoping rules
in perl 5.8.

Function prototypes for perl 5.8

Add prototypes to make perl 5.8 happy

Fix "illegal character in prototype" message.

Since we rerun assign, it can shuffle around the interfaces on a node
even if the node is "fixed".

Fix up last change to makefile to actually do the right thing...

Commit perl event wrapper code generated by the new Swig 1.3.  Also fix
up the makefile to do a better job of detecting the perl version when
compiling these.

The default for the perl SNMP library has apparently changed.

does not handle. Just kill it from the response in osid.info; the caller is
not interested.

much better.

Switch around 'value' and 'defaultvalue' fields for "watchdog/rusage" and
set value field to NULL.

schema.

CR_SERVER_GONE_ERROR). Instead of bailing, sit and loop trying to
reconnect, given that this is known to be a transient error, and we do
not really want our daemons to go belly up during that brief time when
the watchdog is getting it restarted. The query is then resent.

For the perl version of this change, I was a lot more pedantic since
we use this library from a zillion places. Also, there is some special
handling cause of the mysqld watchdog which would become useless if
the test query hung trying to reconnect to the server forever.

As a side effect of this change, we should see way less email when
mysqld goes catanoic since the new code will just loop instead of
generating tons of errors.

Might actually increase overall rebustness. On the other hand, could
end up being a total disaster!

CR_SERVER_GONE_ERROR). Instead of bailing, sit and loop trying to
reconnect, given that this is known to be a transient error, and we do
not really want our daemons to go belly up during that brief time when
the watchdog is getting it restarted.

This turns out to be nice in my elabinelab experiments, where very
idle daemons have a habit of timing out, although there were other
ways to deal with that, but I'm lazy.

Most programs already use that library; getting the stragglers before
I whack the library for mysql 5.X

Most programs already use that library; getting the stragglers before
I whack the library for mysql 5.X

and report the numbers without passing judgement on the results.

This way, the linktest instances can know who will be running linktest
and who will not and thus we can run on a subset of nodes.

there is a query (by Mike I think) that has this form:

          SELECT * FROM t1, t2 JOIN t3 ON  ...

Prior to 5.X, the comma operator had the same precedence as join, and
so it was evaluated left to right. Well, now comma is lower then join
and this query breaks cause the right side is evaluated before the
left side. The solution is simply:

          SELECT * FROM (t1, t2) JOIN t3 ON  ...

but as the manual points out, why not just use:

          SELECT * FROM t1 JOIN t2 JOIN t3 ON ...

and avoid precedence issues.

are now reserved words mysql 5.X. Skip to the next entry ...

5.0 client side is very picky about this.