linux-traipu team mailing list archive

[Henrik Ingo <henrik.ingo@xxxxxxxxxxxxx>]

Correction to the above: Don't patch the plugin.ini file, just do
./configure --disable-js-plugin

This will build the plugin but it is not loaded by default.

** Changed in: drizzle
       Status: New => Invalid

-- 
You received this bug notification because you are a member of UBUNTU -
AL - BR, which is subscribed to Drizzle.
https://bugs.launchpad.net/bugs/971300

Title:
  drizzle: should not abort when a plugin is not available

Status in A Lightweight SQL Database for Cloud Infrastructure and Web Applications:
  Invalid

Bug description:
  For example, when the js plugin is compiled  but not installed (e.g on
  Debian is has to be an extra package as it has build-dependencies are
  only available on certain architectures).

  In this case, when drizzle is installed but the js-plugin package not,
  drizzle fails to start:

  #drizzled
  Can't open shared library '/usr/lib/drizzle7/libjs_plugin.so' (errno: 0 /usr/lib/drizzle7/libjs_plugin.so: Kann die Shared-Object-Datei nicht öffnen: Datei oder Verzeichnis nicht gefunden)
  Couldn't load plugin library named 'js'.

  Aborting:"Failed to initialize plugins". Abort was called from
  drizzled/drizzled.cc:1341 in init_variables_after_daemonizing()

  
  I think this can be handled in a better way, also to better integrate into Distribution packasging (to avoid that if a plugin in removed that the drizzle fails to start without reconfiguration)

  For example, if a plugin is not found, but not explictly enabled, just ignore this. If it is enabled, it should also not fail (if it is not a dependeny on a other installed plugin. It should not fail, because removing a package does not mean that its configuration gets deleted.
  (PHP does it like thos: it warns in the log when it does not find an extension)

  coldtobi

To manage notifications about this bug go to:
https://bugs.launchpad.net/drizzle/+bug/971300/+subscriptions