Emmanuel Cecchet wrote:
The options you are trying to use are not part of the Sequoia 2.9 DTD.
The DTD specifies:
<!ELEMENT SecuritySettings (Jar?, Accept?, Block?, SSL?)>
<!ATTLIST SecuritySettings
defaultConnect (true | false) "true"
>
Note that security settings regarding IP address filtering are going to
be dropped in Sequoia 4. You should better use a firewall to efficiently
deal with this filtering.
Don't hesitate to point obsolete docs and config files so that we can
fix them.
I believe the problem stems from the example controller configuration,
doc/examples/controller-configuration.xml:
<SecuritySettings defaultConnect="true">
<Jar allowAdditionalDriver="true"/>
<Shutdown>
<Client allow="true" onlyLocalhost="true"/>
<Console allow="false"/>
</Shutdown>
<Accept>
<Iprange value="*.*.*.*"/>
</Accept>
</SecuritySettings>
I ran into a similar problem using the examples as a starting point.
Rather than approaching this with a hit or miss correction on report,
why not have someone sign off on each example configuration prior to a
release? If someone can't validate the configuration prior to release,
move the files into an "untested" folder or something. As it is right
now, the examples are completely broken (at least for RAIDb1 with
MySQL). Having them included is simply causing confusion and
frustration in end users that are looking for them for an example to
start from. Not having them would cause far less confusion and
frustration than having them in a broken state.
--
Jamin W. Collins
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
