Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-9426

Develop support library for searching well known filesystem locations for module implementations

    XMLWordPrintableJSON

Details

    • Icon: Task Task
    • Resolution: Won't Do
    • Icon: Major - P3 Major - P3
    • None
    • None
    • Internal Code
    • None

    Description

      We will need a concept of a search path for modules. At the very least, when asked to load a module with no explicit path information, this system should search at least:

      • The CWD of the process. This would be the correct move for things like tests, where the module library is likely to be dropped into the same directory by the build system.
      • <path-to-current-binary>/../libexec. This relies on portably locating the real path of the currently executing binary. From there, we will assume that we are in a 'bin' directory, and that the sibling 'libexec' directory contains our modules.
      • A user configurable directory, specified somehow.

      After searching these locations, the unqualified name should be attempted to fall back to LD_LIBRARY_PATH or the equivalent.

      Attachments

        Activity

          People

            backlog-server-platform DO NOT USE - Backlog - Platform Team
            andrew.morrow@mongodb.com Andrew Morrow (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: