Uploaded image for project: 'MCollective (moved to puppet.atlassian.net)'
  1. MCollective (moved to puppet.atlassian.net)
  2. MCO-548

discontinue use of daemon.bat under PE/Windows

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Major
    • Resolution: Done
    • None
    • None
    • DOCS, PE, RE

    Description

      As summarised by josh in PUP-1802

      In FOSS, there's a service_manager.rb that registers ruby.exe, so that's already good. https://github.com/puppetlabs/marionette-collective/blob/master/ext/windows/service_manager.rb#L34

      In PE, this is handled in the wix installer, and that registers mco_daemon.bat, so that's not good.

      We should change the wix installer to use a similar mechanism for PE as we do for FOSS so there are fewer differences in how we launch things, and also to address the underlying issues raised in PUP-1802

      Attachments

        1. RubyW_launchedFromStartRun.png
          RubyW_launchedFromStartRun.png
          34 kB
        2. MissingEnvVars.png
          MissingEnvVars.png
          79 kB
        3. Adjustments.png
          Adjustments.png
          40 kB

        Issue Links

          relates to

          Bug - A problem which impairs or prevents the functions of the product. FACT-1125 Under certain Windows environments (specifically when run under MCO), libfacter.so cannot be loaded

          • Blocker - Blocks development and/or testing work, production could not run.
          • Closed

          Bug - A problem which impairs or prevents the functions of the product. PUP-1802 Puppet should execute ruby.exe not cmd.exe when running as a windows service

          • Major - Major loss of function.
          • Closed
          links to

          Web Link FTW GH PR #87

          Activity

            People

              rob Rob Reynolds
              richard Richard Clamp
              Ryan Gard Ryan Gard
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Zendesk Support